<div dir="ltr">Hi,<div><br></div><div> I'm said author of the -tail. I'll just add one thing about --tail to what Jonas and Philip have said and that it works intelligently with -c, so '-t' along doesn't put anything to the paste buffer but '-c -t' does. That's logic much easier to add inside of password store than outside of it (and yes, for those not running an agent, I do it with only one decryption).</div>
<div><br></div><div> As a side note, I'm always loath to run 'pass' without -c because I'm not convinced I can actually clear my screen well enough being that I'm running in tmux inside of iTerm, and just too many things that can cache my output. Putting passwords to stdout is last resort for me.</div>
<div><br></div><div>Von</div><div><br></div><div>p.s. I send the patch to this list a few weeks ago, you can find it here:<br></div><div><a href="https://github.com/von-forks/password-store/commit/081774c5cc0cab745c66875c67a66c67d8d45219">https://github.com/von-forks/password-store/commit/081774c5cc0cab745c66875c67a66c67d8d45219</a></div>
<div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 13, 2014 at 7:00 PM, Matthew Cengia <span dir="ltr"><<a href="mailto:mattcen@gmail.com" target="_blank">mattcen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 2014-02-13 09:40, Philip Chase wrote:<br>
> I like the --tail option.<br>
><br>
> I find myself running "pass myAccount" to verify the username. I then run<br>
> "pass -c myAccount", because I don't want to lift my hand to copy the<br>
> password to the scrap.<br>
><br>
> Much as I like the unix philosophy of do one thing and do it well, I've<br>
> always seen it as a guide, not a religion. Would it be so bad to save the<br>
> end user some keystrokes?<br>
><br>
> Eschewing conveniences creates obstacles to adoption. It begs the<br>
> question, "Do we only want a certain type of people to use this software?"<br>
<br>
</div>Of course it's not a hard and fast rule; the benefit of the code has to<br>
be weighed with the code quantity to decide whether it's worthwhile. I<br>
haven't seen the code for --tail, but given your above proposed<br>
use-case, and the fact that Jonas stated that is the author's intended<br>
purpose makes me reconsider my stance on this; it does sound like a<br>
commen enough use-case that it would be worth implementing inside pass.<br>
<br>
For my part, in the immediate term I'd probably just write a shell<br>
function:<br>
<br>
passt(){ pass -c "$1"; pass "$1" | sed 1d;}<br>
<br>
But for every pass user to have to do this is a bit ridiculous when it<br>
could be done within pass.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Regards,<br>
Matthew Cengia<br>
</font></span><br>_______________________________________________<br>
Password-Store mailing list<br>
<a href="mailto:Password-Store@lists.zx2c4.com">Password-Store@lists.zx2c4.com</a><br>
<a href="http://lists.zx2c4.com/mailman/listinfo/password-store" target="_blank">http://lists.zx2c4.com/mailman/listinfo/password-store</a><br>
<br></blockquote></div><br></div></div>