<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That sounds great Eric, those two modifications combined will make finding and repeating old commands much easier!<div class=""><br class=""></div><div class="">Oliver.<br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Oct 1, 2015, at 3:31 PM, Eric Pettersen <<a href="mailto:pett@cgl.ucsf.edu" class="">pett@cgl.ucsf.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I also just tweaked the up/down history navigation so that if the navigation would produce a result identical to whatever is currently in the command line, it “keeps going” until it yields a results that isn’t identical. This applies to both normal up/down and shifted up/down. So, if you have several consecutive identical entries in your command history, this effectively treats them as one entry and therefore may reduce the need for a preference to not record consecutive identical entries in the command history…<div class=""><br class=""></div><div class="">—Eric</div><div class=""><br class=""></div><div class=""><div apple-content-edited="true" class="">
<div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Eric Pettersen</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>UCSF Computer Graphics Lab</div></div>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Oct 1, 2015, at 6:35 AM, Oliver Clarke <<a href="mailto:olibclarke@gmail.com" class="">olibclarke@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Just tried out the new daily build and the command line history autofiltering works great, thanks Eric! This makes it much easier to cycle through previous selection commands, or to remember syntax for previous vop commands.<br class=""><br class=""></div>Cheers,<br class=""></div>Oliver.<br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Sep 30, 2015 at 2:46 PM, Oliver Clarke <span dir="ltr" class=""><<a href="mailto:olibclarke@gmail.com" target="_blank" class="">olibclarke@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class=""><div class="">That sounds great, thanks Eric! I look forward to trying it out, think it'll be a real timesaver!<br class=""><br class=""></div>Cheers,<br class=""></div>Oli.<br class=""></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Sep 30, 2015 at 2:19 PM, Eric Pettersen <span dir="ltr" class=""><<a href="mailto:pett@cgl.ucsf.edu" target="_blank" class="">pett@cgl.ucsf.edu</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Oliver,<br class="">
This seems like a useful suggestion. I have implemented it in a slightly different form. If you use the shift key while navigating the command history (i.e. shift up/down arrow or control-N/P), then it will jump to the next history entry that matches the current command name. Available in the next daily build.<br class="">
<br class="">
—Eric<br class="">
<div class=""><div class=""><br class="">
> On Sep 23, 2015, at 2:42 PM, Oliver Clarke <<a href="mailto:olibclarke@gmail.com" target="_blank" class="">olibclarke@gmail.com</a>> wrote:<br class="">
><br class="">
> Hi all,<br class="">
><br class="">
> Just a suggestion (I guess for chimera 2) - would it be possible to autofilter the command history based on the typed substring?<br class="">
><br class="">
> That is if I have typed “sel” and hit the up arrow, to only cycle through those commands in the history that start with “sel”.<br class="">
><br class="">
> This would be particularly handy for scrolling quickly through recent “sel” and “color” commands - a similar mechanism is implemented in several shells and it works well.<br class="">
><br class="">
> Cheers,<br class="">
> Oliver.<br class="">
</div></div>> _______________________________________________<br class="">
> Chimera-users mailing list<br class="">
> <a href="mailto:Chimera-users@cgl.ucsf.edu" target="_blank" class="">Chimera-users@cgl.ucsf.edu</a><br class="">
> <a href="http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users" rel="noreferrer" target="_blank" class="">http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users</a><br class="">
><br class="">
<br class="">
</blockquote></div><br class=""></div>
</div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></body></html>