From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: Eli Zaretskii <eliz@gnu.org>, Andreas Schwab <schwab@linux-m68k.org>
Cc: 17386@debbugs.gnu.org
Subject: bug#17386: 24.3.90; emacs_abort in cmcheckmagic
Date: Mon, 05 May 2014 12:27:39 +0200 [thread overview]
Message-ID: <5367679B.6040902@yahoo.fr> (raw)
In-Reply-To: <834n171aul.fsf@gnu.org>
Le 03/05/2014 11:16, Eli Zaretskii a écrit :
> 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.
Yes.
Here's a picture of what tmux does :
http://tmux.sourceforge.net/tmux3.png
What I called "status line" is the last one. The different windows are
called 'panes' in tmux parlance.
Btw, I tried another experiment, using "cat", to see if SIGWINCH is sent~:
$ gdb cat
(gdb) handle SIGWINCH print
Signal Stop Print Pass to program Description
SIGWINCH No Yes Yes Window size changed
(gdb) r -
Starting program: /bin/cat -
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
#### At this point I maximized then unmaximized the window.
Program received signal SIGWINCH, Window size changed.
Program received signal SIGWINCH, Window size changed.
[Inferior 1 (process 21202) exited normally]
(gdb)
I tried the same with emacs but saw nothing:
$ gdb emacs
(gdb) handle SIGWINCH print
Signal Stop Print Pass to program Description
SIGWINCH No Yes Yes Window size changed
(gdb) r -Q -nw
Starting program: /usr/local/bin/emacs -Q -nw
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0xb6386b40 (LWP 21216)]
[Thread 0xb673c880 (LWP 21212) exited]
[Inferior 1 (process 21212) exited normally]
(gdb)
There's nothing to see on this transcript, but I did change the window
size after running "r -Q -nw", just like with "cat" above, before
exiting emacs. I don't know what this means.
--
Nico.
next prev parent reply other threads:[~2014-05-05 10:27 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 [this message]
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=5367679B.6040902@yahoo.fr \
--to=theonewiththeevillook@yahoo.fr \
--cc=17386@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.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).