Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Grant Taylor via COFF <coff@minnie.tuhs.org>
To: coff@minnie.tuhs.org
Subject: Re: [COFF] What is your prompt?
Date: Mon, 27 Dec 2021 12:07:08 -0700	[thread overview]
Message-ID: <1aa06132-37d7-126a-e490-5dce6d134ac8@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CANCZdfrKFTjWnNGcZBTBfZ9e379VwjhNJK3Z8mLJR9dKLOj4SA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]

On 12/27/21 11:55 AM, Warner Losh wrote:
> I've taken to doing that via symlinks to the host name (so foo.host 
> with multiple ones symlinked to the master if it comes to that). That 
> way I could keep my local changes in version control... One to many 
> client machines crashing and losing stuff in my past...

I too use <something>.<hostname> where something is aliases, bashrc, 
zshrc, etc.

I will also frequently have <something>.<hostname> source 
<something>.<arbitrary group>.  That way I can have $WORK specific 
things in <something>.<$WORK> and personal things in <something>.home, 
and accounts on friends systems source <something>.<friend's name>. 
Thus I have things common to <arbitrary group> in one file.  It means 
that machine specific <something>.<hostname> ends up being quite 
minimal.  I could probably get away with (sym)links if I don't need 
/anything/ host specific.



-- 
Grant. . . .
unix || die


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

  reply	other threads:[~2021-12-27 19:07 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
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 [this message]
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=1aa06132-37d7-126a-e490-5dce6d134ac8@spamtrap.tnetconsulting.net \
    --to=coff@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    /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).