Databases
StackOverflow2013
Postsdbo
PORunning CVS in console upsets BZR by changing output encoding
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORunning CVS in console upsets BZR by changing output encoding
    primarykey
    data
    text
    <p>I am using both cvs and bzr for versioning and prefer running both in a powershell console. But when I run cvs, it changes the console encoding, which makes bzr throw error messages. I tried setting $OutputEncoding to UTF-8 in my PSProfile and then bzr seems happy... until I run cvs, then bzr starts to complain again - even though $OutputEncoding is the same!?</p> <p>Is there any way to get the two to work in the same console?</p> <pre><code>Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. Visual Studio 2010 Command Prompt variables set. PS W:\&gt; [Console]::OutputEncoding.EncodingName Western European (DOS) PS W:\&gt; bzr st bzr: ERROR: Not a branch: "W:/". PS W:\&gt; [Console]::OutputEncoding.EncodingName Western European (DOS) PS W:\&gt; cvs up cvs update: No CVSROOT specified! Please use the `-d' option cvs [update aborted]: or set the CVSROOT environment variable. PS W:\&gt; [Console]::OutputEncoding.EncodingName Unicode (UTF-8) PS W:\&gt; bzr st bzr: warning: unknown terminal encoding cp65001. Using encoding cp1252 instead. bzr: warning: unknown terminal encoding cp65001. Using encoding cp1252 instead. bzr: ERROR: Not a branch: "W:/". PS W:\&gt; </code></pre> <p>Example with forcing OutputEncoding to UTF8 in the PSProfile.</p> <pre><code>Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved. Visual Studio 2010 Command Prompt variables set. PS W:\&gt; $OutputEncoding BodyName : utf-8 EncodingName : Unicode (UTF-8) HeaderName : utf-8 WebName : utf-8 WindowsCodePage : 1200 IsBrowserDisplay : True IsBrowserSave : True IsMailNewsDisplay : True IsMailNewsSave : True IsSingleByte : False EncoderFallback : System.Text.EncoderReplacementFallback DecoderFallback : System.Text.DecoderReplacementFallback IsReadOnly : True CodePage : 65001 PS W:\&gt; bzr st bzr: ERROR: Not a branch: "W:/". PS W:\&gt; cvs up cvs update: No CVSROOT specified! Please use the `-d' option cvs [update aborted]: or set the CVSROOT environment variable. PS W:\&gt; $OutputEncoding BodyName : utf-8 EncodingName : Unicode (UTF-8) HeaderName : utf-8 WebName : utf-8 WindowsCodePage : 1200 IsBrowserDisplay : True IsBrowserSave : True IsMailNewsDisplay : True IsMailNewsSave : True IsSingleByte : False EncoderFallback : System.Text.EncoderReplacementFallback DecoderFallback : System.Text.DecoderReplacementFallback IsReadOnly : True CodePage : 65001 PS W:\&gt; bzr st bzr: warning: unknown terminal encoding cp65001. Using encoding cp1252 instead. bzr: warning: unknown terminal encoding cp65001. Using encoding cp1252 instead. bzr: ERROR: Not a branch: "W:/". PS W:\&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKenned
    1. USKenned
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThat warning is harmless in your case.
      singulars
      1. PORunning CVS in console upsets BZR by changing output encoding
      1. USbialix
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload