all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jaygkamat@gmail.com, 28568@debbugs.gnu.org
Subject: bug#28568: 26.0.60; [eshell] Incompatible change in alias argument handling
Date: Sat, 30 Sep 2017 20:12:57 -0400	[thread overview]
Message-ID: <877ewfenee.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83zi9c4nm9.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Sep 2017 11:06:06 +0300")

tags 28568 fixed
close 28568
quit

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Noam Postavsky <npostavs@users.sourceforge.net>
>> Date: Fri, 29 Sep 2017 21:45:24 -0400
>> Cc: 28568@debbugs.gnu.org
>> 
>> Here it is, not sure if I've got the texinfo formatting right.  I'm not
>> really clear on the difference between @samp{}, @command{}, and @code{}.
>
> Commands typed by the user should be in @kbd.

Fixed and pushed to emacs-26.

[1: ba9139c501]: 2017-09-30 20:01:33 -0400
  Revert "Don't lose arguments to eshell aliases (Bug#27954)"
  http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=ba9139c501ed8220980e898f127e293e8f263ea1





      reply	other threads:[~2017-10-01  0:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22  6:59 Possible Eshell/Tramp Bug in Emacs 26 Jay Kamat
2017-09-22 20:17 ` Jay Kamat
2017-09-23  8:23   ` bug#28320: " Michael Albinus
2017-09-23 13:21     ` bug#28568: 26.0.60; [eshell] Incompatible change in alias argument handling Noam Postavsky
2017-09-23 14:55     ` bug#28568: 26.0.60; [eshell] Incompatible change in alias argument handling (Was: Possible Eshell/Tramp Bug in Emacs 26) Noam Postavsky
2017-09-27  4:28       ` bug#28568: 26.0.60; [eshell] Incompatible change in alias argument handling Jay Kamat
2017-09-27 12:55         ` Noam Postavsky
2017-09-30  1:45           ` Noam Postavsky
2017-09-30  8:06             ` Eli Zaretskii
2017-10-01  0:12               ` 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=877ewfenee.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=28568@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jaygkamat@gmail.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.