comment on

From the bash man page :

The cmdhist shell option,  if enabled,  causes  the shell  to attempt
to  save each line of a multi-line command in the same history entry,
adding semicolons where necessary to preserve  syntactic correctness. 
The lithist shell option  causes  the shell to save the command  with
embedded newlines instead of semicolons.  See the  description of the
shopt builtin  ...  under  SHELL BUILTIN COMMANDS  for information on
setting  and  unsetting  shell options.
[download]

dug into it and here is the gist:

optional feature of Bash history filtering that isn't always  enabled
by default in distributions is cmdhist. This determines whether multi
-line commands are stored in the history as a single command (on)  or
not (off; default). 

To enable this feature, you would type

      shopt -s cmdhist

To disable this feature, you would type

      shopt -u cmdhist
[download]

not sure if this fixes the prob ... update: script and alias(s) work with cygwin as well

In reply to Re: remember perl one-liners by l3v3l
in thread remember perl one-liners by tinita

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 How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks