From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>,
17386@debbugs.gnu.org, theonewiththeevillook@yahoo.fr
Subject: bug#17386: 24.3.90; emacs_abort in cmcheckmagic
Date: Wed, 28 May 2014 22:47:36 +0200 [thread overview]
Message-ID: <87wqd5fx5j.fsf@yahoo.fr> (raw)
In-Reply-To: <834n09j2c4.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 May 2014 19:27:23 +0300")
>> From: Andreas Schwab <schwab@suse.de>
>> Most likely nothing, since it is supposed to be transparent to the tmux
>> or screen instance.
fwiw, this was confirmed to me on IRC in #tmux.
Eli Zaretskii <eliz@gnu.org> writes:
> How is Emacs supposed to get the screen dimension when tmux is
> attached? It looks like Emacs saw (or maybe fell back on) a 23-line
> text terminal when it expected to see more than that (at least 42)
> from the beginning of the session.
>
> Nicolas, is the screen size supposed to be the same when you detach
> and re-attach, and if so, what size do you expect it to be?
The size of my screen (read : the size of my gnome-terminal frame) can
be different when I detach and when I reattach (because I sometimes
maximize the frame, some other times not -- also because I use screen of
different sizes.)
On my laptop, over ssh:
- when I don't maximize my gnome-terminal frame, then gdb reports:
FrameRows(current_tty) = 23.
- If the gnome-terminal frame is maximized, gdb reports 42.
(In case you wonder, I tried detaching when not-maximized, then
maximizing gnome-terminal and then reattaching : it worked fine.)
--
Nico.
next prev parent reply other threads:[~2014-05-28 20:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 5:08 bug#17386: 24.3.90; emacs_abort in cmcheckmagic Nicolas Richard
2014-05-02 7:28 ` Eli Zaretskii
2014-05-02 8:14 ` Nicolas Richard
2014-05-02 8:58 ` Eli Zaretskii
2014-05-02 9:45 ` Nicolas Richard
2014-05-02 12:09 ` Eli Zaretskii
2014-05-02 15:17 ` Nicolas Richard
2014-05-02 15:42 ` Eli Zaretskii
2014-05-02 16:00 ` Nicolas Richard
2014-05-02 16:17 ` Eli Zaretskii
2014-05-03 6:56 ` Nicolas Richard
2014-05-03 7:18 ` Eli Zaretskii
2014-05-03 8:21 ` Andreas Schwab
2014-05-03 8:53 ` Eli Zaretskii
2014-05-03 8:56 ` Andreas Schwab
2014-05-03 9:16 ` Eli Zaretskii
2014-05-05 10:27 ` Nicolas Richard
2014-05-05 11:11 ` Eli Zaretskii
2014-05-05 11:25 ` Nicolas Richard
2014-05-28 8:35 ` Nicolas Richard
2014-05-28 14:17 ` Eli Zaretskii
2014-05-28 14:41 ` Nicolas Richard
2014-05-28 15:24 ` Andreas Schwab
2014-05-28 16:27 ` Eli Zaretskii
2014-05-28 16:38 ` Andreas Schwab
2014-05-28 20:47 ` Nicolas Richard [this message]
2014-05-29 16:05 ` Eli Zaretskii
2022-04-26 12:56 ` Lars Ingebrigtsen
2022-04-29 7:26 ` Nicolas Richard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-29 10:10 ` Lars Ingebrigtsen
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=87wqd5fx5j.fsf@yahoo.fr \
--to=theonewiththeevillook@yahoo.fr \
--cc=17386@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@suse.de \
/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).