[Bug cli/30497] Bad User Experience with multiple list commands reaching end of file

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Bruno Larsen <blarsen@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f52625f1f29a87e94aa9d40e1b76be2d0ecedc10

commit f52625f1f29a87e94aa9d40e1b76be2d0ecedc10
Author: Bruno Larsen <blarsen@redhat.com>
Date:   Thu Jun 15 11:17:07 2023 +0200

    gdb/cli: Improve UX when using list with no args

    When using "list" with no arguments, GDB will first print the lines
    around where the inferior is stopped, then print the next N lines until
    reaching the end of file, at which point it warns the user "Line X out
    of range, file Y only has X-1 lines.".  This is usually desirable, but
    if the user can no longer see the original line, they may have forgotten
    the current line or that a list command was used at all, making GDB's
    error message look cryptic. It was reported in bugzilla as PR cli/30497.

    This commit improves the user experience by changing the behavior of
    "list" slightly when a user passes no arguments.  It now prints that the
    end of the file has been reached and recommends that the user use the
    command "list ." instead.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30497
    Reviewed-By: Eli Zaretskii <eliz@gnu.org>
    Approved-By: Tom Tromey <tom@tromey.com>

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