unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Anders Munch <ajm@flonidan.dk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "58835@debbugs.gnu.org" <58835@debbugs.gnu.org>
Subject: bug#58835: 28.1; try-complete-file-name-partially modifies text before point
Date: Fri, 28 Oct 2022 14:32:47 +0000	[thread overview]
Message-ID: <HE1PR0502MB300439DF147FFD0E2B4479C4B4329@HE1PR0502MB3004.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <83czacjdco.fsf@gnu.org>

> May I ask what is the real-life situation where this slash conversion caused you trouble?

Any filename occurring in a text document may potentially be copy-pasted into
some other program.  In most other software that I use, filenames abide by the
platform convention, and a filename occurring in a text document may potentially
be copy-pasted into one of these other programs.  For example, into the address
bar of Windows Explorer, or into a file selection dialog.  For those purposes,
backslashes are the platform standard and frontslashes are not accepted.

For that reason, MS Windows filenames that I keep in text files are written
using backslashes.  When I write part of a file/directory name and use
hippie-expand to help write the rest, then the data that I have already entered
manually is changed, and must be hand-edited back.  Which is frustrating and
time-consuming, and has driven me to no longer use hippie-expand for this.

I'm well aware that GNU Emacs's approach to portability is to make all platforms
pretend they're POSIX, so I wasn't expecting much.  I didn't expect the
expansion to be corrected.  I was just hoping the manually entered text to the
left of point could be left unmangled.

regards, Anders






  reply	other threads:[~2022-10-28 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  8:35 bug#58835: 28.1; try-complete-file-name-partially modifies text before point Anders Munch
2022-10-28 13:18 ` Eli Zaretskii
2022-10-28 14:32   ` Anders Munch [this message]
2023-09-02 16:43   ` Stefan Kangas

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=HE1PR0502MB300439DF147FFD0E2B4479C4B4329@HE1PR0502MB3004.eurprd05.prod.outlook.com \
    --to=ajm@flonidan.dk \
    --cc=58835@debbugs.gnu.org \
    --cc=eliz@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 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).