Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

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

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (3)
As of 2021-06-17 17:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    What does the "s" stand for in "perls"? (Whence perls)












    Results (84 votes). Check out past polls.

    Notices?