unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org, Jay Kamat <jaygkamat@gmail.com>,
	28568@debbugs.gnu.org
Subject: bug#28568: 26.0.60; [eshell] Incompatible change in alias argument handling (Was: Possible Eshell/Tramp Bug in Emacs 26)
Date: Sat, 23 Sep 2017 10:55:55 -0400	[thread overview]
Message-ID: <871smxo45g.fsf_-_@users.sourceforge.net> (raw)
In-Reply-To: <87r2uxlt6o.fsf@gmx.de> (Michael Albinus's message of "Sat, 23 Sep 2017 10:23:27 +0200")


> Jay Kamat <jaygkamat@gmail.com> writes:
>>
>> 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!

Another possible alternative is adding "sudo" to
`eshell-complex-commands' (adding `eshell-tramp' to
`eshell-modules-list' does this, see `eshell-tramp-initialize').

    eshell-complex-commands is a variable defined in ‘esh-cmd.el’.
    Its value is ("ls")

      This variable may be risky if used as a file-local variable.

    Documentation:
    A list of commands names or functions, that determine complexity.
    That is, if a command is defined by a function named eshell/NAME,
    and NAME is part of this list, it is invoked as a complex command.
    Complex commands are always correct, but run much slower.  If a
    command works fine without being part of this list, then it doesn’t
    need to be.

    If an entry is a function, it will be called with the name, and should
    return non-nil if the command is complex.

    You can customize this variable.

>> Also, it would be nice if eshell aliases and other configuration were
>> not loaded in an emacs -Q setting.

Yes, that would make sense too.





  parent reply	other threads:[~2017-09-23 14:55 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   ` bug#28320: Possible Eshell/Tramp Bug in Emacs 26 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     ` Noam Postavsky [this message]
2017-09-27  4:28       ` 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=871smxo45g.fsf_-_@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=28568@debbugs.gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jaygkamat@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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).