From: "Ryan C. Thompson" <rct@thompsonclan.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19412@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#19412: 24.3; ido-write-file sometimes writes to a different directory than, it says it will
Date: Mon, 11 Jan 2021 13:50:46 -0500 [thread overview]
Message-ID: <1fc3637a-ef93-0f68-0dfb-a37a575ecbe3@thompsonclan.org> (raw)
In-Reply-To: <87o8hvco12.fsf@gnus.org>
On 1/11/21 1:43 PM, Lars Ingebrigtsen wrote:
> "Ryan C. Thompson" <rct@thompsonclan.org> writes:
>
>> And to do that, we need to preserve the user's current input
>> verbatim when falling back.
> Sounds reasonable, but who knows what people are doing in the setup
> hooks there? So I worry about making a change like this, perhaps overly
> much.
>
> I guess the only way to find out whether it breaks a lot of stuff or
> not is to try it out and get feedback.
>
Yes, it's definitely an invasive change, and more properly characterized
as a work-around than a true fix, so the worry isn't unwarranted. I'm
pretty sure the code is correct (or as close to correct as possible
given the "API" limitations we're working with), but it's always
possible there's some edge case I haven't anticipated.
prev parent reply other threads:[~2021-01-11 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 20:21 bug#19412: 24.3; ido-write-file sometimes writes to a different directory than it says it will Don Morrison
2019-11-03 22:48 ` bug#19412: 24.3; ido-write-file sometimes writes to a different directory than, " Ryan C. Thompson
2019-11-04 14:52 ` Ryan C. Thompson
2019-11-04 15:55 ` Ryan C. Thompson
2020-03-11 16:46 ` Ryan C. Thompson
2020-08-12 16:44 ` Stefan Kangas
2021-01-10 23:12 ` Ryan C. Thompson
2021-01-11 14:14 ` Lars Ingebrigtsen
2021-01-11 14:28 ` Ryan C. Thompson
2021-01-11 18:43 ` Lars Ingebrigtsen
2021-01-11 18:50 ` Ryan C. Thompson [this message]
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=1fc3637a-ef93-0f68-0dfb-a37a575ecbe3@thompsonclan.org \
--to=rct@thompsonclan.org \
--cc=19412@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).