From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Samer Masterson <samer@samertm.com>
Cc: 19391@debbugs.gnu.org
Subject: bug#19391: [PATCH] bug#19391: 25.0.50; eshell-buffer-shorthand breaks command dollar expansion
Date: Sun, 26 Nov 2017 21:42:45 -0500 [thread overview]
Message-ID: <87a7z8o316.fsf@users.sourceforge.net> (raw)
In-Reply-To: <1425455434.1450.1@mail.samertm.com> (Samer Masterson's message of "Tue, 03 Mar 2015 23:50:34 -0800")
tags 19391 fixed
close 19391 25.1
quit
Samer Masterson <samer@samertm.com> writes:
> - The syntax for the shorthand should be distinct from any other
> lisp objects, so that we don't have to put out fires when people try
> to do things that are valid but overlap with the shorthand (e.g. this
> bug was caused by eshell's external shell feature redirecting to a
> symbol.) Something like #<name-of-buffer> would work.
> - The shorthand should be processed as a buffer (similar to how #
> <buffer name-of-buffer> is processed). That means the shorthand won't
> require extra code anywhere except for the reader.
> - The shorthand should be on by default, and probably shouldn't have
> an option to disable it. The reason for this is that the shorthand
> would be universally beneficial and backwards compatible, and making
> it controlled by an option is inviting bugs when we shouldn't be.
Something along these lines was pushed for Emacs 25.
[1: e37da5a4a8]: 2015-05-17 14:28:51 -0700
eshell: Introduce new buffer syntax
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=e37da5a4a8055826f0fc1051083495a828509672>
prev parent reply other threads:[~2017-11-27 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 4:35 bug#19391: 25.0.50; eshell-buffer-shorthand breaks command dollar expansion dylan
2015-02-24 10:59 ` bug#19391: [PATCH] " Samer Masterson
2015-03-03 15:56 ` Eli Zaretskii
2015-03-04 7:50 ` Samer Masterson
2015-03-04 17:28 ` Eli Zaretskii
2017-11-27 2:42 ` Noam Postavsky [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7z8o316.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=19391@debbugs.gnu.org \
--cc=samer@samertm.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.