From: "Paul D. Swasey" <ps3u+@andrew.cmu.edu>
To: rc@archone.tamu.edu
Subject: format of the history file
Date: Mon, 16 Dec 1991 20:42:58 -0600 [thread overview]
Message-ID: <Added.AdHKF6u00Ui3JWN05R@andrew.cmu.edu> (raw)
Since blank lines are not added to the history file, rc could put
a newline after each command and programs that do multi-line command
editing could be made... just a thought.
Unfortunatley, history() is called on a line-by-line basis... maybe
it wouldn't be worth the trouble to find a suitable place to append a
newline to the history file (I'm hoping someone more familiar with
rc internals can find a not-so-ugly place to add such a thing).
-dave
reply other threads:[~1991-12-17 2:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Added.AdHKF6u00Ui3JWN05R@andrew.cmu.edu \
--to=ps3u+@andrew.cmu.edu \
--cc=rc@archone.tamu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).