public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30420] New: [gdb/emacs] Maint info screen in emacs Date: Thu, 04 May 2023 09:26:12 +0000 [thread overview] Message-ID: <bug-30420-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30420 Bug ID: 30420 Summary: [gdb/emacs] Maint info screen in emacs Product: gdb Version: HEAD Status: NEW Severity: minor Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I had the idea to try out "maint info screen" in the gdb mode of emacs. Firstly, I have a terminal with: ... $ echo $LINES 28 $ echo $COLUMNS 118 $ echo $TERM xterm ... After starting /usr/bin/emacs -nw, and doing M-x gdb, and executing "gdb -i=mi", I get: ... (gdb) maint info screen Number of characters gdb thinks are in a line is 116. Number of characters readline reports are in a line is 115. Number of characters curses thinks are in a line is 118. Number of characters environment thinks are in a line is 117 (COLUMNS). Number of lines gdb thinks are in a page is 4294967295 (unlimited). Number of lines readline reports are in a page is 32767 (unlimited). Number of lines curses thinks are in a page is 25. Number of lines environment thinks are in a page is 25 (LINES). (gdb) shell echo $TERM dumb (gdb) ... I was a bit bewildered by the 115/116/117/118. I'm hoping this'll make more sense once PR30346 is fixed. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-05-04 9:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-04 9:26 vries at gcc dot gnu.org [this message] 2023-05-22 16:35 ` [Bug gdb/30420] " vries at gcc dot gnu.org
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=bug-30420-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).