# Interactive rebase encoding 5 messages from 2008-12-15 to 2008-12-15. Participants: Constantine Plotnikov, Miklos Vajna, Johannes Schindelin. Thread: https://gitlist.dev/t/16734 ## Constantine Plotnikov, 2008-12-15 12:42 Subject: Interactive rebase encoding Message-ID: <85647ef50812150442n48609eadl4f3e47fcc715e643@mail.gmail.com> URL: https://gitlist.dev/e/85647ef50812150442n48609eadl4f3e47fcc715e643%40mail.gmail.com ``` The interactive rebase command builds a text file and passes it to editor specified as environment variable or as configuration parameter. However the man page for rebase operation says nothing about which encoding will be used for that file. Apparently i18n.logoutputencoding is used. I think that the man page for rebase operation should explicitly specify it. Also it might make sense to use explicit encoding parameter for interactive rebase operation. Constantine ``` ## Miklos Vajna, 2008-12-15 15:13 Subject: Re: Interactive rebase encoding Message-ID: <20081215151322.GI5691@genesis.frugalware.org> URL: https://gitlist.dev/e/20081215151322.GI5691%40genesis.frugalware.org In-Reply-To: <85647ef50812150442n48609eadl4f3e47fcc715e643@mail.gmail.com> ``` On Mon, Dec 15, 2008 at 03:42:08PM +0300, Constantine Plotnikov wrote: > The interactive rebase command builds a text file and passes it to > editor specified as environment variable or as configuration > parameter. However the man page for rebase operation says nothing > about which encoding will be used for that file. Apparently > i18n.logoutputencoding is used. I think that the man page for rebase > operation should explicitly specify it. Care to send a patch? > Also it might make sense to use explicit encoding parameter for > interactive rebase operation. Do you have a use-case where having a different encoding for log output and rebase -i todo list makes sense? Thanks. ``` ## Johannes Schindelin, 2008-12-15 15:54 Subject: Re: Interactive rebase encoding Message-ID: URL: https://gitlist.dev/e/alpine.DEB.1.00.0812151652400.30769%40pacific.mpi-cbg.de In-Reply-To: <85647ef50812150442n48609eadl4f3e47fcc715e643@mail.gmail.com> ``` Hi, On Mon, 15 Dec 2008, Constantine Plotnikov wrote: > The interactive rebase command builds a text file and passes it to > editor specified as environment variable or as configuration parameter. > However the man page for rebase operation says nothing about which > encoding will be used for that file. Apparently i18n.logoutputencoding > is used. As rebase -i does nothing else than piping the output of git log into a file (at least this is the first step), I thought it would be obvious that it uses the output encoding preferred by the user. Indeed, I cannot think of any scenario where it might make sense to have a different encoding in git rebase -i than in git log. Ciao, Dscho ``` ## Constantine Plotnikov, 2008-12-15 16:21 Subject: Re: Interactive rebase encoding Message-ID: <85647ef50812150821g4a032af0u31425fd7f4c0fd9@mail.gmail.com> URL: https://gitlist.dev/e/85647ef50812150821g4a032af0u31425fd7f4c0fd9%40mail.gmail.com In-Reply-To: ``` On Mon, Dec 15, 2008 at 6:54 PM, Johannes Schindelin wrote: > Hi, > > On Mon, 15 Dec 2008, Constantine Plotnikov wrote: > >> The interactive rebase command builds a text file and passes it to >> editor specified as environment variable or as configuration parameter. >> However the man page for rebase operation says nothing about which >> encoding will be used for that file. Apparently i18n.logoutputencoding >> is used. > > As rebase -i does nothing else than piping the output of git log into a > file (at least this is the first step), I thought it would be obvious that > it uses the output encoding preferred by the user. Yes. That was my first hypothesis, but I had to check it through small experiment and source code examination. And if consider the bug described in the thread http://kerneltrap.org/mailarchive/git/2008/11/11/4063184, the hypothesis might have been incorrect. > > Indeed, I cannot think of any scenario where it might make sense to have a > different encoding in git rebase -i than in git log. > For IDE, it might make sense to force UTF-8 encoding instead of using currently configured logoutputencoding. Currently the extra call to git config is needed to check expected encoding of the file before data could be shown to the user. Also user specified encoding might fail to display some characters in commit messages that was encoded using other encodings, forcing UTF-8 would have also fixed this problem as well. BTW for IDEs an option that causes non-abbreviated commit hashes would have been useful as well. Constantine ``` ## Johannes Schindelin, 2008-12-15 16:56 Subject: Re: Interactive rebase encoding Message-ID: URL: https://gitlist.dev/e/alpine.DEB.1.00.0812151755040.30769%40pacific.mpi-cbg.de In-Reply-To: <85647ef50812150821g4a032af0u31425fd7f4c0fd9@mail.gmail.com> ``` Hi, On Mon, 15 Dec 2008, Constantine Plotnikov wrote: > On Mon, Dec 15, 2008 at 6:54 PM, Johannes Schindelin > wrote: > > > > Indeed, I cannot think of any scenario where it might make sense to > > have a different encoding in git rebase -i than in git log. > > For IDE, it might make sense to force UTF-8 encoding instead of using > currently configured logoutputencoding. I consider rebase -i to be porcelain, and as such not suitable to be used as a backend for an IDE. Help the git-sequencer effort if you want a plumbing. Ciao, Dscho ```