From: Joey Arthur <jgarthur@stanford.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26087@debbugs.gnu.org, Joey Arthur <jgarthur@stanford.edu>
Subject: bug#26087: 24.5; graphical glitches when splitting window
Date: Tue, 14 Mar 2017 09:58:49 -0700 [thread overview]
Message-ID: <CAHk2AgJzy-U_MbkiXTMHXoeyFYyR8RVGwRgxEShGVEngRaCYEg@mail.gmail.com> (raw)
In-Reply-To: <83pohkbkpl.fsf@gnu.org>
Thanks for the clarification.
Yes, this problem only happens in a text mode-session -- the GUI
session is fine.
I've checked the report-emacs-bug template while running on our login
node (which works fine) and the computation node (which gives the
graphical glitches). The only difference outside of memory usage is
this line under "Recent messages" which only appears in the fully
functioning session:
Loading /usr/share/emacs/site-lisp/site-start.d/rpmdev-init.el (source)...done
Seems pretty innocuous though
On Mon, Mar 13, 2017 at 8:28 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Joey Arthur <jgarthur@stanford.edu>
>> Date: Mon, 13 Mar 2017 14:29:55 -0700
>> Cc: Joey Arthur <jgarthur@stanford.edu>, 26087@debbugs.gnu.org
>>
>> > Is that a text-mode session? Looks like bug#17497, or something
>> > similar.
>>
>> I don't believe so -- this happens when splitting the window from the
>> initial *GNU Emacs* buffer, which looks to be in fundamental-mode.
>
> Sorry for being unclear: I meant text-mode session, as in
> "emacs -nw", s opposed to a GUI session. That is, the display
> is on a text terminal, right?
next prev parent reply other threads:[~2017-03-14 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 18:17 bug#26087: 24.5; graphical glitches when splitting window Joey Arthur
2017-03-13 20:43 ` Eli Zaretskii
2017-03-13 21:29 ` Joey Arthur
2017-03-14 3:28 ` Eli Zaretskii
2017-03-14 16:58 ` Joey Arthur [this message]
2021-12-01 18:55 ` bug#26087: 24.5; 'emacs -nw' - " Lars Ingebrigtsen
2021-12-29 3:05 ` Stefan Kangas
2021-12-29 3:21 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHk2AgJzy-U_MbkiXTMHXoeyFYyR8RVGwRgxEShGVEngRaCYEg@mail.gmail.com \
--to=jgarthur@stanford.edu \
--cc=26087@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.