From: John Mastro <john.b.mastro@gmail.com>
To: 26229@debbugs.gnu.org, Manuel Uberti <manuel.uberti@inventati.org>
Subject: bug#26229: 26.0.50; shell-mode: turning off input echoing
Date: Fri, 24 Mar 2017 10:49:05 -0700 [thread overview]
Message-ID: <CAOj2CQSFMkJQkhJV7GzPpY5Va-0mR8=aB=6JdAQPsM0wvd9Cug@mail.gmail.com> (raw)
In-Reply-To: <9f23704e-d176-56f6-ce23-2fc5335f6c65@inventati.org>
Hi Manuel,
Manuel Uberti <manuel.uberti@inventati.org> wrote:
> thanks for the quick reply. I'm afraid your solution doesn't fix
> the problem for me. Could it depend on the shell I'm using? I'm using
> the Fish shell.
I haven't used fish before but I don't think it should be a problem.
I tried to reproduce the problem in Emacs 26.0.50 (commit 211d41a) with
fish 2.3.1 on Fedora 25 but it worked correctly for me.
I started emacs with "emacs -Q", then pasted the following into the
*scratch* buffer and evaluated it:
(setq explicit-shell-file-name (executable-find "fish"))
(defun my-init-shell-mode ()
(setq comint-process-echoes t))
(with-eval-after-load 'shell
(add-hook 'shell-mode-hook #'my-init-shell-mode))
I then invoked `M-x shell', confirmed I was using fish, and typed a few
commands, none of which echoed the command.
Just to be sure, perhaps it's worth trying again, and confirm that the
value of `comint-process-echoes' is t in the shell buffer? You can check
it's value by invoking `M-: comint-process-echoes RET' while the shell
buffer is current.
John
next prev parent reply other threads:[~2017-03-24 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 20:32 bug#26229: 26.0.50; shell-mode: turning off input echoing Manuel Uberti
2017-03-23 21:27 ` John Mastro
2017-03-24 5:29 ` Manuel Uberti
2017-03-24 17:49 ` John Mastro [this message]
2017-03-25 17:57 ` Manuel Uberti
2017-03-25 18:13 ` npostavs
2017-03-25 18:19 ` Manuel Uberti
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='CAOj2CQSFMkJQkhJV7GzPpY5Va-0mR8=aB=6JdAQPsM0wvd9Cug@mail.gmail.com' \
--to=john.b.mastro@gmail.com \
--cc=26229@debbugs.gnu.org \
--cc=manuel.uberti@inventati.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).