From: bk@analytikerna.se (Bengt KLEBERG)
To: rc@archone.tamu.edu
Subject: 1 (global) history file
Date: Tue, 27 Aug 1991 03:32:49 -0500 [thread overview]
Message-ID: <9108270832.AA22315@analytikerna.se> (raw)
----- Begin Included Message -----
|Byron mentioned last week that he uses one history file for all his
|windows; i tried this last week, and now say i think it is the way to go.
I tried this in the beginning, but it seemed to jumble up and loose
entries from the history file randomly. It could get into situations
where I'd type a command into one window, and then right after it type
a -p, and it wouldn't find the command. Does anyone else use a single
global history under Ultrix and have it work? (Boyd?)
- cks
----- End Included Message -----
At the very begining I tried to change to several history files. The
coding was simple but I didn't like the result so I switched back to
one file. I've not had any problems with using one global history file
for all my windows (and on all the machines in the network) at the same
time. Maybe I don't write enough commands. We use sunos 4.1.1
Bengt
next reply other threads:[~1991-08-27 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-27 8:32 Bengt KLEBERG [this message]
1991-08-27 17:39 ` John Mackin
[not found] <91Aug28.114551cdt.22537@archone.tamu.edu>
1991-08-28 17:42 ` John Mackin
1991-08-30 17:17 ` Chris Siebenmann
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=9108270832.AA22315@analytikerna.se \
--to=bk@analytikerna.se \
--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).