From: "Theodore Ts'o" <tytso@mit.edu>
To: Warner Losh <imp@bsdimp.com>
Cc: Rudi Blom <rudi.j.blom@gmail.com>, coff <coff@minnie.tuhs.org>
Subject: Re: [COFF] What is your prompt?
Date: Sun, 26 Dec 2021 20:33:13 -0500 [thread overview]
Message-ID: <YckX2doEZOeEjx/h@mit.edu> (raw)
In-Reply-To: <CANCZdfoP6bkJCMTD96p=iEH8YP9cq1vX9TfXDASu0egmPYGVfQ@mail.gmail.com>
On Sun, Dec 26, 2021 at 02:33:03PM -0700, Warner Losh wrote:
> I have symlinks to all my files. I also have special hooks that I run per
> os and per host to pull in different configs when needed. Though in
> recent years I've not needed it much. I used to do a lot for work like
> this, but these days work envs are close to my home env, so there is little
> point.
I have a bunch of work-specific aliases which get picked up via:
if [ -f $HOME/.bashrc.local ] ; then
. $HOME/.bashrc.local
fi
I don't keep .bashrc.local under git control, since some of the paths
in those aliases might be considered Work-confidential, so I don't
want to push them out to a personal git repo.
> I've been doing this since RCS days across 5 different SCMs... git makes
> oopses so rare that the paranoia below seems overkill. Though for other
> SCMs it would likely not be paranoid enough.
The backup directory isn't for paranoia, actually. It's so the first
time that I install my custom dotfiles on a particular machine, if
there is a prexisting dot-file, say, .profile, I copy it to the backup
directory before replacing it with a symlink to the dotfiles repo.
There might be some magic environment variables or PATH setup that is
unique to that particular system's default dot files, so I can take a
quick look at them and see if I might need to extend my generic dot
files, or maybe add something to the ~/.bashrc.local file, or some
such.
- Ted
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-12-27 1:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 2:50 Rudi Blom
2021-12-25 4:40 ` Theodore Ts'o
2021-12-25 17:39 ` Steffen Nurpmeso
2021-12-25 18:28 ` Grant Taylor via COFF
2021-12-25 19:14 ` Steffen Nurpmeso
2021-12-26 3:44 ` Grant Taylor via COFF
2021-12-25 23:19 ` Greg 'groggy' Lehey
2021-12-25 23:43 ` Steffen Nurpmeso
2021-12-26 21:18 ` Theodore Ts'o
2021-12-26 21:33 ` Warner Losh
2021-12-27 1:33 ` Theodore Ts'o [this message]
2021-12-27 2:52 ` Rudi Blom
2021-12-27 3:43 ` Greg 'groggy' Lehey
2021-12-27 4:06 ` Rudi Blom
2021-12-27 4:12 ` Greg 'groggy' Lehey
2021-12-27 4:28 ` Rudi Blom
2021-12-27 18:44 ` Steffen Nurpmeso
2021-12-27 18:55 ` Warner Losh
2021-12-27 19:07 ` Grant Taylor via COFF
2021-12-27 19:25 ` Steffen Nurpmeso
2021-12-27 18:37 ` Steffen Nurpmeso
2021-12-26 3:29 ` Grant Taylor via COFF
2021-12-26 3:54 ` Greg 'groggy' Lehey
2021-12-26 5:27 ` Grant Taylor via COFF
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 6:59 [COFF] What is your prompt? (was: ksh88 source code?) Andy Kosela
2021-12-24 17:17 ` [COFF] What is your prompt? Grant Taylor via COFF
2021-12-26 22:17 ` Mike Markowski
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=YckX2doEZOeEjx/h@mit.edu \
--to=tytso@mit.edu \
--cc=coff@minnie.tuhs.org \
--cc=imp@bsdimp.com \
--cc=rudi.j.blom@gmail.com \
/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).