From: Eli Zaretskii <eliz@gnu.org>
To: Jack Kamm <jackkamm@gmail.com>
Cc: 34815-done@debbugs.gnu.org
Subject: bug#34815: 26.1; read-shell-command globally sets comint-input-autoexpand to 'history
Date: Fri, 15 Mar 2019 11:16:28 +0200 [thread overview]
Message-ID: <834l841or7.fsf@gnu.org> (raw)
In-Reply-To: <87tvg99ls0.fsf@jaheira.i-did-not-set--mail-host-address--so-tickle-me> (message from Jack Kamm on Mon, 11 Mar 2019 13:52:15 -0700)
> From: Jack Kamm <jackkamm@gmail.com>
> Cc: 34815@debbugs.gnu.org
> Date: Mon, 11 Mar 2019 13:52:15 -0700
>
> Yes, replacing setq with setq-local seems to fix the issue.
Thanks, I installed such a change on the emacs-26 branch.
prev parent reply other threads:[~2019-03-15 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 18:08 bug#34815: 26.1; read-shell-command globally sets comint-input-autoexpand to 'history jackkamm
2019-03-11 18:41 ` Eli Zaretskii
2019-03-11 20:52 ` Jack Kamm
2019-03-15 9:16 ` Eli Zaretskii [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
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=834l841or7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34815-done@debbugs.gnu.org \
--cc=jackkamm@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 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).