Re: [lldb-dev] Break setting aliases...

> On Jul 23, 2020, at 1:51 AM, Pavel Labath wrote: > > On 22/07/2020 19:50, Jim Ingham wrote: >>> On Jul 22, 2020, at 12:34 AM, Pavel Labath wrote: >>> >>> The "--" is slightly unfortunate, but it's at least consistent with our >>> other commands taking raw input. We could avoid that by makin

Re: [lldb-dev] Break setting aliases...

On 22/07/2020 19:50, Jim Ingham wrote: >> On Jul 22, 2020, at 12:34 AM, Pavel Labath wrote: >> >> The "--" is slightly unfortunate, but it's at least consistent with our >> other commands taking raw input. We could avoid that by making the >> command not take raw input. I think most of the "modes"

Re: [lldb-dev] Break setting aliases...

BTW: to see what things expand to after reach regex alias, just set this setting first: (lldb) settings set interpreter.expand-regex-aliases true Each time you type "b main" it will show you the expansion: (lldb) b main breakpoint set --name 'main' ... (lldb) b main.cpp:12 breakpoint set --file

Re: [lldb-dev] Break setting aliases...

> On Jul 22, 2020, at 12:34 AM, Pavel Labath wrote: > > I use "b" for file+line breakpoints and "br set -n" for function > breakpoints, mainly because I couldn't be bothered to figure out how > that works with the "b" command. Now that I have studied the command > once again, I may try using it

Re: [lldb-dev] Break setting aliases...

> On Jul 22, 2020, at 9:57 AM, Dave Lee wrote: > > On Tuesday, July 21, 2020, Jim Ingham via lldb-dev > wrote: > I think adding: > > bs (break source) -> break set -y > ba (break address) -> break set -a > bn (break name) -> break set -n > > would provide a co

Re: [lldb-dev] Break setting aliases...

On Tuesday, July 21, 2020, Jim Ingham via lldb-dev wrote: > I think adding: > > bs (break source) -> break set -y > ba (break address) -> break set -a > bn (break name) -> break set -n > > would provide a convenient way to set the most common classes of > breakpoints while not precluding access t

Re: [lldb-dev] Break setting aliases...

I use "b" for file+line breakpoints and "br set -n" for function breakpoints, mainly because I couldn't be bothered to figure out how that works with the "b" command. Now that I have studied the command once again, I may try using it for function breakpoints as well... I don't have any hard object

Re: [lldb-dev] Break setting aliases...

> On Jul 21, 2020, at 2:54 PM, Greg Clayton wrote: > > > >> On Jul 21, 2020, at 10:22 AM, Jim Ingham via lldb-dev >> wrote: >> >> When we were first devising commands for lldb, we tried to be really >> parsimonious with the one & two letter unique command strings that lldb >> ships with

Re: [lldb-dev] Break setting aliases...

> On Jul 21, 2020, at 10:22 AM, Jim Ingham via lldb-dev > wrote: > > When we were first devising commands for lldb, we tried to be really > parsimonious with the one & two letter unique command strings that lldb ships > with by default. I was trying to leave us as much flexibility as possib

Re: [lldb-dev] Break setting aliases...

> On Jul 21, 2020, at 11:13 AM, Jonas Devlieghere wrote: > > I don't mind adding the two-letter commands, but I also don't really see the > value in being able to say `bs` instead of `b s -y`. Until either becomes > muscle memory, both require a little cognitive overhead of thinking > "break

Re: [lldb-dev] Break setting aliases...

I don't mind adding the two-letter commands, but I also don't really see the value in being able to say `bs` instead of `b s -y`. Until either becomes muscle memory, both require a little cognitive overhead of thinking "breakpoint set -y" or "breakpoint source". As a user there would be more value

[lldb-dev] Break setting aliases...

When we were first devising commands for lldb, we tried to be really parsimonious with the one & two letter unique command strings that lldb ships with by default. I was trying to leave us as much flexibility as possible as we evolved, and I also wanted to make sure we weren’t taking up all the