From: Barry OReilly <gundaetiapo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14408@debbugs.gnu.org
Subject: bug#14408: 24.3.50; *Messages* buffer no longer updates automatically
Date: Thu, 16 May 2013 14:08:58 -0400 [thread overview]
Message-ID: <CAFM41H1Uqg6pHrVcYeahb27BzG3rwJaXRxty6ZmAq8dJLvNeqQ@mail.gmail.com> (raw)
In-Reply-To: <831u96u9c9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
Looking further, there are a couple circumstances where it won't reproduce:
• There needs to be newlines after the message call to reproduce
• eval-last-sexp needs to be invoked through a local keymap
Let ~/emacs-local-key.el contain:
(local-set-key (kbd "<f5>") 'eval-last-sexp)
Or you can do so in an emacs-lisp-mode-hook.
Steps:
• Run: ./src/emacs -Q --load ~/emacs-local-key.el
• C-x 3
• M-x buffer-menu
• Select *Messages* (now left window is *Messages* right is *scratch*)
• C-x o
• Input: (message "a")
• Enter a couple times so as there are new lines after the message call
• Move point to after the close paren above
• Use f5 to eval-last-sexp, no change in *Messages*
• C-x o
• Now all the "a" messages appear
I tried sizing the window to the left and to the right, still can reproduce.
Using emacs -nw I can reproduce it.
I'm on RHEL 5 OS.
[-- Attachment #2: Type: text/html, Size: 1042 bytes --]
next prev parent reply other threads:[~2013-05-16 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 13:03 bug#14408: 24.3.50; *Messages* buffer no longer updates automatically Barry OReilly
[not found] ` <handler.14408.B.13686230477730.ack@debbugs.gnu.org>
2013-05-16 15:37 ` bug#14408: Acknowledgement (24.3.50; *Messages* buffer no longer updates automatically) Barry OReilly
2013-05-16 17:24 ` bug#14408: 24.3.50; *Messages* buffer no longer updates automatically Eli Zaretskii
2013-05-16 17:30 ` Glenn Morris
2013-05-16 18:21 ` Drew Adams
2013-05-16 18:34 ` Eli Zaretskii
2013-05-16 18:08 ` Barry OReilly [this message]
2013-05-16 18:37 ` Eli Zaretskii
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=CAFM41H1Uqg6pHrVcYeahb27BzG3rwJaXRxty6ZmAq8dJLvNeqQ@mail.gmail.com \
--to=gundaetiapo@gmail.com \
--cc=14408@debbugs.gnu.org \
--cc=eliz@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).