Re: [lldb-dev] Command history query

2017-04-19 Thread Jim Ingham via lldb-dev
Yeah, source-code twiddling of thumbs while waiting for a build to complete... Jim > On Apr 19, 2017, at 4:51 PM, Zachary Turner wrote: > > Scratch that, looks like you already fixed this. > > On Wed, Apr 19, 2017 at 4:50 PM Zachary Turner wrote: > I'll take a look > > On Wed, Apr 19, 2017

Re: [lldb-dev] Command history query

2017-04-19 Thread Zachary Turner via lldb-dev
Scratch that, looks like you already fixed this. On Wed, Apr 19, 2017 at 4:50 PM Zachary Turner wrote: > I'll take a look > > On Wed, Apr 19, 2017 at 10:33 AM Jim Ingham via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> No, this was an inadvertent side effect of rewriting the command parser

Re: [lldb-dev] Command history query

2017-04-19 Thread Zachary Turner via lldb-dev
I'll take a look On Wed, Apr 19, 2017 at 10:33 AM Jim Ingham via lldb-dev < lldb-dev@lists.llvm.org> wrote: > No, this was an inadvertent side effect of rewriting the command parser to > use llvm's StringRef's. Please file a bug (or submit a patch!) > > Jim > > > On Apr 18, 2017, at 10:49 PM, vi

Re: [lldb-dev] Command history query

2017-04-19 Thread Jim Ingham via lldb-dev
No, this was an inadvertent side effect of rewriting the command parser to use llvm's StringRef's. Please file a bug (or submit a patch!) Jim > On Apr 18, 2017, at 10:49 PM, via lldb-dev wrote: > > Hello, > > The query to repeat a command from history used to be ! but > it looks like that d