<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 22, 2020, at 9:57 AM, Dave Lee <<a href="mailto:davelee.com@gmail.com" class="">davelee.com@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On Tuesday, July 21, 2020, Jim Ingham via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think adding:<br class="">
<br class="">
bs (break source) -> break set -y<br class="">
ba (break address) -> break set -a<br class="">
bn (break name) -> break set -n<br class="">
<br class="">
would provide a convenient way to set the most common classes of breakpoints while not precluding access to all the other options available to “break set”. <br class="">
</blockquote><div class=""><br class=""></div><div class="">If these are defined as regular aliases, I wonder how many people would try, say, `bn -H whatever` and be confused when it doesn't work because it didn't do the right thing (such as creating a breakpoint named "-H" in this example). Should these new aliases support flags before and after the positional argument? Personally I think so. But to support that, it seems they'd need to be implemented with `command regex`. In that case, would it be good to add similar before/after flag composition abilities to `b` as Greg Clayton suggested?</div></div></blockquote><div><br class=""></div><div>Grrr… Apparently command aliases don’t work quite how I intended them to. I thought the intent was that:</div><div><br class=""></div><div>(lldb) command alias breakpoint set -y %1</div><div><br class=""></div><div>would put the first argument into the %1 position, not the first command word. That way you could preserve the position independence of options. But that’s not what it does. %1 is just the first command word (-H in your example).</div><div><br class=""></div><div>The way it works now, mine is not a useful suggestion. When I have some time I’ll play around with how to make that work, until then we can keep discussing the _regex_break command, but the aliases I started out with are unappealing.</div><div><br class=""></div><div>Jim</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""></div><div class="">It hasn't been mentioned in this thread, but `b` has undocumented handling for flags: the prefix `b -` is expanded to `breakpoint set -`. Because of this I almost never use `breakpoint set` directly. For whatever it's worth, this means `bn` can be achieved as `b -n`, etc. As Pavel Labath suggested, I think it's worth updating the help documentation for `b` to explicitly lead users from `b` to `breakpoint set`.</div><div class=""><br class=""></div><div class="">Dave</div>
</div></blockquote></div><br class=""></body></html>