From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: theonewiththeevillook@yahoo.fr, 17386@debbugs.gnu.org
Subject: bug#17386: 24.3.90; emacs_abort in cmcheckmagic
Date: Sat, 03 May 2014 12:16:02 +0300 [thread overview]
Message-ID: <834n171aul.fsf@gnu.org> (raw)
In-Reply-To: <877g631brz.fsf@igel.home>
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: theonewiththeevillook@yahoo.fr, 17386@debbugs.gnu.org
> Date: Sat, 03 May 2014 10:56:00 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Can we be sure that tmux reserves its line via that ioctl?
>
> What do you mean with "reserves its line"?
What Nicolas reported (I know nothing about tmux, so cannot say this
better, sorry):
> tmux shows some sort of status line, which means that the client
> (emacs-in-gdb in my case) sees one line less.
and
> I tried splitting tmux (because of the related bug bug#16674) :
> (gdb) p FrameRows(current_tty)
> $4 = 20
>
> (that's in the lower pane ; in the one above the answer is 21)
My understanding from this was that tmux reserves one screen line for
its status, and also that it can split a TTY into several portions,
each one emulating a separate terminal.
next prev parent reply other threads:[~2014-05-03 9:16 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 [this message]
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
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=834n171aul.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17386@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=theonewiththeevillook@yahoo.fr \
/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).