all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleksandr Gavenko <gavenkoa@gmail.com>
Cc: 28924@debbugs.gnu.org
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 00:37:56 +0300	[thread overview]
Message-ID: <CAFNJpni-3RHFUKO9Vwh7SovDDJAZy_qOgscH703gR-Kxm+pwNQ@mail.gmail.com> (raw)
In-Reply-To: <83y3o08nnz.fsf@gnu.org>

On Tue, Oct 24, 2017 at 8:24 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> All changelog entries placed on one line on vc-print-root-log for HG with \n
>> symbols between entries.
>>
>> When I changed:
>>
>>  (defcustom vc-hg-root-log-format
>>    `(,(concat "{rev}:{ifeq(branch, 'default','', '{branch}')}"
>>               ":{bookmarks}:{tags}:{author|person}"
>> -             " {date|shortdate} {desc|firstline}\\n")
>> +             " {date|shortdate} {desc|firstline}\n")
>>
>> it starts working fine.
>
> I tried to reproduce this, but couldn't.  Can you show a complete
> recipe, starting with "emacs -Q", and using some public hg repository
> one can clone?
>
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.

Actually everything with backslash escaping is broken when CYGWIN=noglob.

I live with:

+  ;; Workaround for Cygwin shell, when set 'CYGWIN=noglob'. By
default 'shell-quote-argument'
+  ;; quoted by double '\' chars this cause failure.
+  (defun shell-quote-argument (argument)
+    (concat "'" argument "'"))

since 2011-08-05 and this has only one drawback - when quoted string
contains single quote...

Most of the time it's not a problem. Sometime I forget about this and
debugging session refreshes my memory when I face a problem ))

Cygwin Emacs w32 is not stable to day long usage. Due to BLODA fork()
it sticks once or twice a day.

Ideally I would like to have Cygwin Emacs with native Windows exec()
instead of unstable fork(). Emacs isn't server app that is needed the
fork().

Native Emacs don't have pty (and M-x term) and lack of smooth
integration with Cygwin. I use cygwin-mount.el and wrappers with .exe
suffix around Cygwin scripts to increase Emacs usefulness...

Without CYGWIN=noglob Emacs fail on some vc-hg.el commands as commands
passes '{rev}' and curly braces from native application are expanded
(stripped) by Cygwin apps.

Windows is extremely unpleasant platform for Emacs usage. With stable
Cygwin Emacs w32 this can be changed ))

Now we have Cygwin Emacs with native Windows widgets (emacs-w32). In
Cygwin list maintainer responded that it would accept patch for
replacing gam_server.exe with native port to Windows API to detect
file changes.

I would like to replace each Emacs Cygwin fork() with exec(). I'll ask
on dev list if it's possible and acceptable when I have enough spare
time for experiment.





  reply	other threads:[~2017-10-24 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21 15:17 bug#28924: 25.3; All hg entries on single line possibly due to typo in vc-hg-root-log-format gavenkoa
2017-10-24 17:24 ` Eli Zaretskii
2017-10-24 21:37   ` Oleksandr Gavenko [this message]
2017-10-24 22:01     ` Ken Brown
2017-10-25 10:50       ` Oleksandr Gavenko
2017-10-25 14:46     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFNJpni-3RHFUKO9Vwh7SovDDJAZy_qOgscH703gR-Kxm+pwNQ@mail.gmail.com \
    --to=gavenkoa@gmail.com \
    --cc=28924@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.