From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: simenheg@runbox.com, monnier@IRO.UMontreal.CA,
40940@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#40940: 27.0.91; project-query-replace-regexp stops too early
Date: Wed, 29 Apr 2020 19:44:59 +0300 [thread overview]
Message-ID: <83mu6uxmus.fsf@gnu.org> (raw)
In-Reply-To: <874kt2l0sx.fsf@gmx.de> (message from Michael Albinus on Wed, 29 Apr 2020 18:22:06 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: dgutov@yandex.ru, simenheg@runbox.com, monnier@IRO.UMontreal.CA,
> 40940@debbugs.gnu.org
> Date: Wed, 29 Apr 2020 18:22:06 +0200
>
> > My patch only calls expand-file-name on local file names. For remote
> > file names, I've left the result of the call to file-remote-p
> > unaltered. Would that be a problem if the file name, after stripping
> > the remote protocol parts, started with "~/" ? And if so, what should
> > be done here about these cases?
>
> Call `expand-file-name' on the remote file name, like
> '(expand-file-name "/ssh:user@host:~/")'. Tramp expands it to
> "/ssh:user@host:/home/user/", in case the "/home/user" is the home
> directory of "user" on "host".
Thanks.
Dmitry, this means my change should be reworked to call
expand-file-name before file-local-name, right?
next prev parent reply other threads:[~2020-04-29 16:44 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mu6uxmus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).