Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I'm sure I could, but I prefer to have it filtered through some conscious, deliberate selection process — not everything I type in any shell I open is worth being preserved... and storing everything would likely only reduce the signal-to-noise ratio. Also, the semi-automatic approach encourages me to add notes or keywords, which tend to improve the overall usefulness of the history files (you know, when you're lazy, you have to devise ways to trick yourself into doing things you otherwise wouldn't do...:)  And honestly, spending one or two seconds when you've finished something (or before you close a shell) to decide whether it's worth being preserved, is not too much of an issue for me. But, as always, YMMV.

Actually, the tools I use to 'manage' my history files are slightly more flexible than what I mentioned above (I can specify how many most recent entries to save, whether to create a new file or append it to some other, whether to open it up in my editor, or filter out common trivialities, etc.), but I didn't want to bore you with the details...

BTW, other than that, I'm pretty old-fashioned in that I very much like paper and pencil to sketch design diagrams or write down temporary todo lists, etc. For one, it just feels better to be able to physically cross out completed items, rather than simply deleting the respective entries in an electronic version (yes, you guessed it, I'm a little weird at times :)

In reply to Re: preserving shell command histories (was Re^2: Work practices: log books, notes files...) by almut
in thread Work practices: log books, notes files... by doom

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others pondering the Monastery: (5)
    As of 2018-06-20 02:42 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (116 votes). Check out past polls.