From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54470@debbugs.gnu.org
Subject: bug#54470: 29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion
Date: Sun, 27 Mar 2022 19:29:43 -0700 [thread overview]
Message-ID: <271c20ca-b226-d29a-b54c-7d7be0ee5a1e@gmail.com> (raw)
In-Reply-To: <ba2464ee-2b95-47c2-bbcf-0a9c55e98572@gmail.com>
On 3/20/2022 1:57 PM, Jim Porter wrote:
> On 3/20/2022 12:05 AM, Eli Zaretskii wrote:
>> The use of quotes 'like this', here and elsewhere in a similar
>> context, begs the question: how to specify names that have embedded
>> single-quote characters in them?
>
> "Very carefully." :)
>
> Seriously though, this is an area I don't fully understand yet, but in
> which I've found several bugs (or at least I think they're bugs). As
> such, I intentionally avoided documenting this since it's pretty
> confusing.
I narrowed down one of the bugs I mentioned here (and fixed it): bug#54603.
There are still a few other issues with quoting/escaping in argument
predicates/modifiers. I can work on fixing these in a separate bug, or
update my patches in this bug if you prefer. I lean very slightly
towards the former, since the quoting/escaping logic could use some
changes to be more consistent. That seems different enough from this bug
that I think it'd be simpler to separate them. That said, if you'd
prefer I do this all in this bug, that's ok too.
next prev parent reply other threads:[~2022-03-28 2:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 1:34 bug#54470: 29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion Jim Porter
2022-03-20 7:05 ` Eli Zaretskii
2022-03-20 20:57 ` Jim Porter
2022-03-28 2:29 ` Jim Porter [this message]
2022-03-30 4:47 ` Jim Porter
2022-03-31 7:19 ` Eli Zaretskii
2022-04-01 4:11 ` Richard Stallman
2022-04-02 5:10 ` Jim Porter
2022-04-15 12:56 ` Eli Zaretskii
2022-04-16 4:57 ` Jim Porter
2022-04-16 10:30 ` Eli Zaretskii
2022-04-16 17:14 ` Jim Porter
2022-04-17 7:32 ` Eli Zaretskii
2022-04-17 18:38 ` Jim Porter
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=271c20ca-b226-d29a-b54c-7d7be0ee5a1e@gmail.com \
--to=jporterbugs@gmail.com \
--cc=54470@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).