On Thu, 31 Oct 2013 10:03:25 +
Roddie Grant gitl...@myword.co.uk wrote:
I have a file on my web server which BBedit shows as UTF-8. It
includes proper curly apostophes and quotation marks.
When I do git diff in Terminal I get output like:
-pE2809CSurfexPlusE2809D is OCCAE28099s
On 31/10/2013 10:20, Konstantin Khomoutov wrote:
On Thu, 31 Oct 2013 10:03:25 +
Roddie Grant gitl...@myword.co.uk wrote:
I have a file on my web server which BBedit shows as UTF-8. It
includes proper curly apostophes and quotation marks.
When I do git diff in Terminal I get output like:
On Thu, 31 Oct 2013 10:51:11 +
Roddie Grant gitl...@myword.co.uk wrote:
[...]
When I do git diff in Terminal I get output like:
-pE2809CSurfexPlusE2809D is OCCAE28099s
[...]
Care to tell us which OS is that?
[...]
Another question: do you see this in a pager or plainly rendered by
On 31/10/2013 12:00, Konstantin Khomoutov wrote:
On Thu, 31 Oct 2013 10:51:11 +
Roddie Grant gitl...@myword.co.uk wrote:
[...]
When I do git diff in Terminal I get output like:
-pE2809CSurfexPlusE2809D is OCCAE28099s
[...]
Care to tell us which OS is that?
[...]
Another question: do
On Thu, 31 Oct 2013 13:23:50 +
Roddie Grant gitl...@myword.co.uk wrote:
[...]
For the record, I had to use 'git --no-pager diff' rather 'git diff
--no-pager'. It solved the problem, but I was connected to the server.
Using 'setenv LESSCHARSET utf-8' works, but only when I've ssh-ed to
On 31/10/2013 14:45, Konstantin Khomoutov wrote:
On Thu, 31 Oct 2013 13:23:50 +
Roddie Grant gitl...@myword.co.uk wrote:
[...]
For the record, I had to use 'git --no-pager diff' rather 'git diff
--no-pager'. It solved the problem, but I was connected to the server.
Using 'setenv
