I might be the only living one who has the expansion of $? in $PS1. (And who's "~/.shrc" gives a _somewhat_ portable PS1 with last-component-of HOSTNAME and PWD.) --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)

Grant Taylor wrote in <517271a2-c18c-f6b2-e5a8-0f93b2accba7(a)spamtrap.tnetconsulting.net>et>: |On 12/25/21 10:39 AM, Steffen Nurpmeso wrote: |> I might be the only living one who has the expansion of $? in $PS1. | |It's not $PS1, but I do have $? in my Zsh $RPROMPT. | |I used to have $? in $PS1 before switching to $RPROMPT. | |> (And who's "~/.shrc" gives a _somewhat_ portable PS1 with |> last-component-of HOSTNAME and PWD.) | |I'd like to know more. | |I don't know if it's a good thing or not, but portability across |platforms (OSs / architectures) is much less of an issue for me than it |was in my last job. Now I mostly worry about Linux and FreeBSD. |Admittedly, some really old versions. Sure. Oh the compatibility of shells i meant, of course. But that mostly colours, now that ~/.profile ensures HOSTNAME and LOGNAME per se. No more \XY escapes here, except \e and the \[..\] that some need (to get it column counting right, with colours) (SHTYPE=bash and =yash). And the "set -o" you need/can to get where you want to be, ksh for example braceexpand, emacs-usemeta (if possible), expand_aliases (bash), cdprint/emacs/tabcomplete (NetBSD ksh). It is of course all a bitrot-affine compatibility mess. You look for $0, sometimes deeper for some *_VERSION, for $OSTYPE (which my ~/.profile sets, too). But in the end it is all a mess. If i recall correctly i once proposed a standardized VERSION or xy thing so that one could easily identify, even in subshells. But that would affect future shells only, anyhow. At one time i have thrown away a lot of tests, since fish and some other shells i will never use no more, what remains is just enough to start working the best i can with dash, bash, ksh. Last change on PS1 in March 2018, i usually only have one account per $HOSTNAME. Pretty bitter is shells without aliases, where the a-lia-ses have to be created as sh_ell_functions. And then one says builtin, the other says built-in. Yeah i mean computing would be nice, if there would not be those uncountable quirks you need in real life. The maintainer of libinput has written a short down-to-earth article on that a few years ago. That reminds me of my bitter gut feeling that something bad will happen, all these days, but luckily the rocket that carried some real penis lifted successfully. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)

On Saturday, 25 December 2021 at 20:29:31 -0700, COFF wrote: If I have a process misbehaving on that tty, I can use the information to run ps against the tty. It's not exactly a daily occurrence, but it's convenient when it's needed. Greg -- Sent from my desktop computer. Finger grog(a)lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php

On Friday, 24 December 2021 at 23:40:56 -0500, Theodore Ts'o wrote: That's actually surprisingly like mine, though I squeeze it into one line. Like you, I find user, system and cwd important, but also the tty. In addition I put a marker to help find prompts in long output, so a typical prompt might be: === grog@bilbo (/dev/pts/27) ~/src 6 -> That's generated with PS1="\[ESC[34m\]=== \u@\h (`tty`) \[ESC[31m\]\w\[ESC[34m\] \# ->\[ESC[30m\]\[ESC[47m\] " That's interesting. How do you do that? Greg -- Sent from my desktop computer. Finger grog(a)lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php

On Sun, Dec 26, 2021 at 12:43:37AM +0100, Steffen Nurpmeso wrote: I keep a private git repo on one of my machines, so when I get a HOST account, I run a comand like this: % git clone ssh://tytso@example.com/home/tytso/repos/dotfiles . % cd dotfiles % make This installs a bunch of symlinks from dotfiles/{.bashrc,.profile,.muttrc}, etc. to $HOME/. That way, I can run "git pull" to update my dotfiles on one particular machine, and if I make local changes, I'll do a "git push" to send them back to my dotfiles repo. The Makefile I have in my top-level repo some folks might find interesting: .PHONY: all bin dotfiles all: dotfiles DIRS= .gnupg .mutt .config/gce-xfstests .config/gcloud/configurations bin em #DBG= echo dotfiles: for file in $(shell find $(CURDIR) -maxdepth 1 -type f -name ".*" \ -not -name ".*~" -not -name ".gitignore" -print); do \ f=$$(basename $$file); \ if test -f $(HOME)/$$f -a ! -h $(HOME)/$$f ; then \ mkdir -p backup ; \ mv $(HOME)/$$f backup ; \ fi ; \ $(DBG) ln -sfn $$file $(HOME)/$$f; \ done for dir in $(DIRS) ; do \ $(DBG) mkdir -p $(HOME)/$$dir ; \ for file in $$(find $$(pwd)/$$dir -maxdepth 1 -type f \ -not -name "*~" -print); do \ f=$$(basename $$file); \ if test -f $(HOME)/$$dir/$$f -a ! -h $(HOME)/$$dir/$$f ; then \ mkdir -p backup/$$dir ; \ mv $(HOME)/$$dir/$$f backup/$$dir ; \ fi ; \ $(DBG) ln -sfn $$file $(HOME)/$$dir/$$f; \ done; \ done if test -d backup ; then find backup -type f -print ; fi Cheers, - Ted

On Sun, Dec 26, 2021 at 02:33:03PM -0700, Warner Losh wrote: 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. 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

On Monday, 27 December 2021 at 9:52:24 +0700, Rudi Blom wrote: That's the architecture. Wouldn't just `uname` be better? I have: case `uname` in Linux) PATH=.:~:/usr/local/bin:/usr/local/sbin:~/bin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/X11R6/bin:/usr/local/bitkeeper:/Photos/Tools export SHELL=/bin/bash ;; NetBSD) PATH=.:~:/usr/pkg/bin::/usr/local/bin:/usr/local/sbin:~/bin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/X11R6/bin:/usr/local/bitkeeper:/usr/local/gnu-autotools/bin:~:/Photos/Tools export SHELL=/usr/pkg/bin/bash ;; FreeBSD) PATH=.:~:/home/local/bin:/usr/local/bin:/usr/local/sbin:~/bin:/usr/bin:/usr/sbin:/bin:/sbin:/Photos/Tools:~ export SHELL=/usr/local/bin/bash ;; ... And yes, lm, if you're looking, there's really a /usr/local/bitkeeper in there. It's been years, but I don't tidy these things up very often. I only just removed mosaic from my fvwm2 config menus. Greg -- Sent from my desktop computer. Finger grog(a)lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php

On Monday, 27 December 2021 at 11:06:07 +0700, Rudi Blom wrote: That looks good to me. And I thought that uname without parms always defaults to uname -s. Greg -- Sent from my desktop computer. Finger grog(a)lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php

Warner Losh wrote in <CANCZdfoP6bkJCMTD96p=iEH8YP9cq1vX9TfXDASu0egmPYGVfQ(a)mail.gmail.com>om>: |On Sun, Dec 26, 2021, 2:18 PM Theodore Ts'o <tytso(a)mit.edu> wrote: |> On Sun, Dec 26, 2021 at 12:43:37AM +0100, Steffen Nurpmeso wrote: |>> I usually do "scp .* HOST:" whenever i get a HOST account, and |>> forget about it thereafter. |> |> I keep a private git repo on one of my machines, so when I get a HOST |> account, I run a comand like this: |> |> % git clone ssh://tytso@example.com/home/tytso/repos/dotfiles . | |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'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 Oh yes, i could not agree more. I never tried bitkeeper ;), but even after eleven years of git (~/calendar (symlink) just told me 12/24 Beschließe öffentliche Projekte mit GIT zu managen (2010) ) i often state "when have i told the last time that git is magnificent?" when it rebases automatically over long history, garbage-collects into one big pack (alongside those i want to .keep unchanged), or selectively distributes branches here and there. Wording spread they furtherly improved the merge algorithm just recently. |SCMs it would likely not be paranoid enough. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)

On 12/27/21 11:55 AM, Warner Losh wrote: 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

Theodore Ts'o wrote in &lt;YcjcC7x8TrMq4kvy(a)mit.edu&gt;du>: |On Sun, Dec 26, 2021 at 12:43:37AM +0100, Steffen Nurpmeso wrote: |> I usually do "scp .* HOST:" whenever i get a HOST account, and |> forget about it thereafter. | |I keep a private git repo on one of my machines, so when I get a HOST |account, I run a comand like this: | |% git clone ssh://tytso@example.com/home/tytso/repos/dotfiles . |% cd dotfiles |% make | |This installs a bunch of symlinks from |dotfiles/{.bashrc,.profile,.muttrc}, etc. to $HOME/. | |That way, I can run "git pull" to update my dotfiles on one particular |machine, and if I make local changes, I'll do a "git push" to send |them back to my dotfiles repo. Negative.. but i have sort of this for root accounts, less any fancy make(1) mechanism, however, but there is ~/sic/root.git, and locally i merge/bundle according branches into machine specific branche(s) that can then be pushed/fetched. (My spare "wales" even simply selectively shares the filesystem via snapshots, it is just which /root/.git branch is checked out, and one "/root/bin/backup.sh restore" after FS synchronization; same shared static kernel, but different ssh keys and /etc/hosts, hostname via kernel command line, thanks to /dev/mapper even /etc/fstab is identical. I can git merge "kent" into "wales", and git just does it right!) I "only have symlinks" in my non-root ~/, but i have to create them manually. I do not have many accounts i work with: practically all VMs for building+testing software, so not much effort getting cosy there. Here on "kent" i created them on April 13th 2019, only added .irssi on April 22nd once i started using IRC, too. That is manageable. And all the directories that then exist nonetheless, ~/sic, ~/{,sec.}arena, ~/$USR (~/usr-kent-crux-linux-x86_64/{bin,lib..} here) are created by ~/.profile when i login the first time with the symlink tree present. (But of course they are empty, hm.) It all _is_ in a sec.arena/configs.git directory, but there is home/ as well as .home/ and some others, and only home/ content is to be distributed, so i go into that home and scp(1). The data in there is pretty stable, and what changes sometimes, for example my mailer's config when its development continues, or the .cwmrc just got a "pkill -CONT tmux" last week (^Z delivery sometimes hits tmux not the terminal within where it is typed), is needed only locally. But your approach is much nicer. Just to add that ~/sic is an encfs mount of ~/.sic, ~/.mozilla of ~/.secweb-mozilla (normal browsing container mounts a specific /home partition), and ~/sec.arena of ~/.sec.arena, only the latter two of which are permanently mounted when the lid is up. Really, i love what has become possible with modern hard- and software! |The Makefile I have in my top-level repo some folks might find |interesting: | |.PHONY: all bin dotfiles | |all: dotfiles | |DIRS= .gnupg .mutt .config/gce-xfstests .config/gcloud/configurations \ |bin em |#DBG= echo | |dotfiles: | for file in $(shell find $(CURDIR) -maxdepth 1 -type f -name ".*" \ | -not -name ".*~" -not -name ".gitignore" -print); do \ | f=$$(basename $$file); \ | if test -f $(HOME)/$$f -a ! -h $(HOME)/$$f ; then \ | mkdir -p backup ; \ | mv $(HOME)/$$f backup ; \ | fi ; \ | $(DBG) ln -sfn $$file $(HOME)/$$f; \ | done | for dir in $(DIRS) ; do \ | $(DBG) mkdir -p $(HOME)/$$dir ; \ | for file in $$(find $$(pwd)/$$dir -maxdepth 1 -type f \ | -not -name "*~" -print); do \ | f=$$(basename $$file); \ | if test -f $(HOME)/$$dir/$$f -a ! -h $(HOME)/$$dir/$$f ; then \ | mkdir -p backup/$$dir ; \ | mv $(HOME)/$$dir/$$f backup/$$dir ; \ | fi ; \ | $(DBG) ln -sfn $$file $(HOME)/$$dir/$$f; \ | done; \ | done | if test -d backup ; then find backup -type f -print ; fi --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)