[Bug cli/30529] New: [gdb/cli] Quitting paging quits gdb

[Bug cli/30529] New: [gdb/cli] Quitting paging quits gdb

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30529

            Bug ID: 30529
           Summary: [gdb/cli] Quitting paging quits gdb
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Consider starting gdb in a small window, say:
...
$ echo $COLUMNS 
38
$ echo $LINES
13
$ gdb
...

We get a paging prompt:
...
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
--Type <RET> for more, q to quit, c to continue without paging--
...
and when we type q, we have:
...
Quit
$ 
...

Thinking about it, this sort of makes sense, if we type 'q', the current
command is aborted, and the current command at that point is, well, just gdb. 
If we quit that, then we quit gdb.

Still, I didn't expect it, I was expecting a gdb prompt, not a shell prompt.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug cli/30529] [gdb/cli] Quitting paging quits gdb

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30529

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
We could either disable the pager during the welcome,
or catch a quit here and have gdb carry on.
The current behavior makes sense in the logic of the code,
but I think is pretty unexpected as a user.

-- 
You are receiving this mail because:
You are on the CC list for the bug.