Steve Borho wrote: > On Mon, Jul 18, 2011 at 9:32 AM, Yuya Nishihara <[email protected]> wrote: > > PARK, Kyung-Kook wrote: > >> I tested this again on my other computer running > >> TortoiseHg 2.1.1 and the same OS ( Windows 7 x64 ). > >> There was no problem. > >> > >> But I still have the problem on my labtop and > >> downgrading to 2.0.5 eliminates the problem. > >> And coming back to 2.1.1 revives it again. > >> > >> What could be possibly wrong? > >> > >> Is there anyway I can track down what is going on myself? > >> > >> Kyung > >> > >> > >> On Thu, Jul 14, 2011 at 18:23, PARK, Kyung-Kook <[email protected]> wrote: > >> > After updating 2.1.1 ( Windows x64 ), > >> > file names in multi-byte are updated to broken names. > >> > > >> > For reproduction, > >> > 1. Add a Korean-named file in repository and commit. > >> > 2. Update to the previous revision which does not have the file. > >> > ( At this point, the committed Korean-named file does not disappear. ) > >> > 3. Update back to the latest revision and the file gets updated to some > >> > broken name. And the file in the right name is still there too. > > > > Where the broken and ghost files appear? In TortoiseHg dialog or > > Windows Explorer? > > > > Could you provide the complete names of those files in binary format? > > something like the following, if you've installed python: > > > > C:\Your\Repo> python.exe > >>>> import os > >>>> os.listdir('.') > > ['.hg', '\xe3\x81\xb0\xe3\x83\xbc', '\xe3\x81\x84', '.hgsub'] > > > >> > I also tried this from command line and there was no problem. > >> > This bug seems new from 2.1.1 because I used the > >> > previous version of thg quite long without problem. > > > > What if running from command-line *still* TortoiseHg windows is open? > > Kyung and I have been discussing this through private chat. This is > what appeared to happen: > > 1) one repository on his disk had fixutf8 enabled > 2) the Workbench in 2.1.x is opening all local repositories at > startup, unless subrepo display is disabled. This is loading every > extension. > > What he is seeing is the side effect of having fixutf8 loaded, but not > enabled on the repository he is using. > > In effect, fixutf8 must be enabled globally in his Mercurial.ini file, > or nowhere at all.
Ah, got it. Thanks for clearing my head. :) Regards, Yuya ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
