From: Dmitry Alexandrov <321942@gmail.com>
To: 26894@debbugs.gnu.org
Subject: bug#26894: 25.1, 26.0.50; ‘eshell/which’ abuses ‘describe-function’
Date: Fri, 12 May 2017 05:18:52 +0300 [thread overview]
Message-ID: <87d1belsvn.fsf@gmail.com> (raw)
‘eshell/which’ in its part, that locates built-in commands (‘$ which which’ for example) and elisp functions in general, looks like a dirty hack [0]: it calls interactive ‘describe-function’ command and parses *Help* buffer.
I encounered two user-visible consequences of this, which perceived as bugs by me:
— When ‘*Help*’ buffer is configured to be shown in a dedicated frame (e. g. (setq pop-up-frames t)), every ‘$ which <build-in command>’ generates a new frame and do not close it.
- When ‘*Help*‘ buffer is already opened, ‘$ which <build-in command>’: (1) raises the frame where it’s opened; (2) kills it, losing its history ([back] / [forward]).
[0] http://git.sv.gnu.org/gitweb/?p=emacs.git;a=blob;f=lisp/eshell/esh-cmd.el;hb=cee4128#l1151
next reply other threads:[~2017-05-12 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 2:18 Dmitry Alexandrov [this message]
2017-06-04 2:50 ` bug#26894: 25.1, 26.0.50; ‘eshell/which’ abuses ‘describe-function’ npostavs
2017-06-04 3:47 ` npostavs
2017-06-24 20:20 ` npostavs
2017-06-28 0:38 ` npostavs
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=87d1belsvn.fsf@gmail.com \
--to=321942@gmail.com \
--cc=26894@debbugs.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).