bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#28924: 25.3; All hg entries on single line possibly due to typo in v


From: Eli Zaretskii
Subject: bug#28924: 25.3; All hg entries on single line possibly due to typo in vc-hg-root-log-format.
Date: Wed, 25 Oct 2017 17:46:50 +0300

> From: Oleksandr Gavenko <gavenkoa@gmail.com>
> Date: Wed, 25 Oct 2017 00:37:56 +0300
> Cc: 28924@debbugs.gnu.org
> 
> Hi! I troubleshooted another issue recently and found that
> CYGWIN=noglob option cause problem when arguments passed from native
> Windows app (Emacs) to Cygwin app.
> 
> In our situation with my fix \n resolved to new line character code by
> Emacs and Cygwin is happy with it. With double slashes single one is
> passed (with "n") to Cygwin application and I see long:
> 
> 1544:::tip:Oleksandr Gavenko 2017-10-23 Make function silent if file
> is modified.\n1543::::Oleksandr Gavenko 2017-10-22 Prefer Python 3 for
> interactive shell.\n1542::::Oleksandr Gavenko 2017-10-21 Use UTF-8 on
> Windows fpr processes.\n1541::::Oleksandr Gavenko 2017-10-11 Set font
> size depending on DPI.\n1540::::Oleksandr Gavenko 2017-10-10 Mistaken
> s-TAB key binding broke my workflow.\n.......
> 
> That is native Emacs with Cygwin wrapper to Cygwin hg. It can be that
> no one on a planet works like that. I believe that people use native
> ports of HG/GIT/ag/ack/etc.

Thanks for telling us.

Since your situation is very special, and since vc-hg-root-log-format
is a defcustom, I think for you to customize the value to make it work
in your setup is exactly the right solution of this problem.  So I'm
closing this bug report, as I think nothing has to be done for it in
Emacs core.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]