From: Michael Albinus <michael.albinus@gmx.de>
To: Jay Kamat <jaygkamat@gmail.com>
Cc: help-gnu-emacs@gnu.org, 28320@debbugs.gnu.org,
npostavs@users.sourceforge.net
Subject: bug#28320: Possible Eshell/Tramp Bug in Emacs 26
Date: Sat, 23 Sep 2017 10:23:27 +0200 [thread overview]
Message-ID: <87r2uxlt6o.fsf@gmx.de> (raw)
In-Reply-To: <87a81mjxmz.fsf@gmail.com> (Jay Kamat's message of "Fri, 22 Sep 2017 16:17:56 -0400")
Jay Kamat <jaygkamat@gmail.com> writes:
Hi Jay,
> It seems that the fix to
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27954 (commit
> e66e81679c3c91d6bf8f62c7abcd968430b4d1fe) caused this issue. I had an
> eshell alias defined as
>
> alias sudo eshell/sudo $*
>
> Which seems to no longer work (with the error described).
There's also bug#28320, which seems to report the same problem.
> Now, the entry:
>
> alias sudo eshell/sudo
>
> works for my purposes instead.
>
> This is a little bit annoying since it means that I can't share these
> aliases across emacs25 and emacs26 without problems. One solution I
> could do is setting `eshell-prefer-lisp-functions' instead of using this
> alias, but I would have liked to only override sudo (and leave the rest
> as system). If anyone knows a better solution, let me know!
>
> Also, it would be nice if eshell aliases and other configuration were
> not loaded in an emacs -Q setting.
Noam, could you have a look on this?
> -Jay
Best regards, Michael.
next parent reply other threads:[~2017-09-23 8:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fubfjk10.fsf@gmail.com>
[not found] ` <87a81mjxmz.fsf@gmail.com>
2017-09-23 8:23 ` Michael Albinus [this message]
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
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=87r2uxlt6o.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=28320@debbugs.gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=jaygkamat@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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).