From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: simenheg@runbox.com, michael.albinus@gmx.de,
monnier@IRO.UMontreal.CA, 40940@debbugs.gnu.org
Subject: bug#40940: 27.0.91; project-query-replace-regexp stops too early
Date: Wed, 29 Apr 2020 19:04:04 +0300 [thread overview]
Message-ID: <83r1w6xoqz.fsf@gnu.org> (raw)
In-Reply-To: <356f1c60-6072-d624-51b3-3e97a6e06253@yandex.ru> (message from Dmitry Gutov on Wed, 29 Apr 2020 18:42:41 +0300)
> Cc: simenheg@runbox.com, monnier@IRO.UMontreal.CA, 40940@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 29 Apr 2020 18:42:41 +0300
>
> >> The patch seems okay, but could you describe a case when the shell fails
> >> to expand '~/'? Is that about cmd.exe? Cygwin?
> >
> > I've bumped into it with cmd.exe on MS-Windows, yes.
>
> I see. Then LGTM, thank you.
Thanks, pushed to the emacs-27 branch.
> Could you clarify, though, does that mean that no project commands are
> currently working on Windows, without this patch? Or does that only
> affect the "transient" project type?
Only the "transient" projects, AFAICT. At least I tried with a Git
repository under ~/, and got absolute file names in the list. I hope
Mercurial does the same. You can test it easily by running
(project-files (project-current t))
in a suitable set up directory.
next prev parent reply other threads:[~2020-04-29 16:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 14:35 bug#40940: 27.0.91; project-query-replace-regexp stops too early Simen Heggestøyl
2020-04-29 3:54 ` Dmitry Gutov
2020-04-29 7:35 ` Eli Zaretskii
2020-04-29 8:29 ` Simen Heggestøyl
2020-04-29 8:37 ` Eli Zaretskii
2020-04-29 9:24 ` Eli Zaretskii
2020-04-29 10:41 ` Eli Zaretskii
2020-04-29 20:53 ` Dmitry Gutov
2020-04-30 20:16 ` Juri Linkov
2020-05-01 6:00 ` Eli Zaretskii
2020-05-01 6:57 ` Eli Zaretskii
2020-05-01 15:27 ` Dmitry Gutov
2020-05-01 15:45 ` Eli Zaretskii
2020-05-01 23:21 ` Dmitry Gutov
2020-05-02 6:44 ` Eli Zaretskii
2020-05-02 7:56 ` Eli Zaretskii
2020-05-03 1:43 ` Dmitry Gutov
2020-05-03 6:54 ` Simen Heggestøyl
2020-05-03 17:10 ` Eli Zaretskii
2020-05-03 17:28 ` Dmitry Gutov
2020-05-03 23:58 ` Dmitry Gutov
2020-04-29 14:50 ` Dmitry Gutov
2020-04-29 14:59 ` Eli Zaretskii
2020-04-29 15:42 ` Dmitry Gutov
2020-04-29 16:04 ` Eli Zaretskii [this message]
2020-04-29 16:11 ` Dmitry Gutov
2020-04-29 15:49 ` Michael Albinus
2020-04-29 15:58 ` Dmitry Gutov
2020-04-29 16:10 ` Eli Zaretskii
2020-04-29 16:22 ` Michael Albinus
2020-04-29 16:44 ` Eli Zaretskii
2020-04-29 18:20 ` Dmitry Gutov
2020-04-29 18:38 ` Michael Albinus
2020-04-29 19:09 ` Dmitry Gutov
2020-04-29 19:15 ` Michael Albinus
2020-04-29 19:26 ` Eli Zaretskii
2020-04-29 18:44 ` Eli Zaretskii
2020-04-29 18:56 ` Michael Albinus
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=83r1w6xoqz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40940@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=michael.albinus@gmx.de \
--cc=monnier@IRO.UMontreal.CA \
--cc=simenheg@runbox.com \
/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.