¹ https://en.m.wikipedia.org/wiki/Business_Process_Model_and_N...
7,427 karma · joined February 3, 2014
[ my public key: https://keybase.io/jnrowe; my proof: https://keybase.io/jnrowe/sigs/orH3nyNqAK4vkIpcxn2HRihHPV2HX80SyDwM9cR5xnw ]
¹ https://en.m.wikipedia.org/wiki/Business_Process_Model_and_N...
> this is a social game of negotiating meaning, and of noticing that language which seems so precise is often not that at all.
I keep coming back to that every time I'm trying to have one of these conversations with people, especially when the question is deeper than whether a salad is a vehicle(as if that were possible).
https://talkingmathwithkids.com/blog/vehicle-chat-invitation...
or discussed in audio form
https://aperiodical.com/2020/08/mathematical-objects-a-vehic...
It strikes me that I treat the result of git-rerere as a ridiculously weak version of this. I'll occasionally carry an unwanted integration branch simply to handle changes that could be managed correctly if there was a better way to express relationships in my tools. Having the functionality baked in to the graph with the associated strictness, and available across clone boundaries would be great.
¹ https://www.cs.tufts.edu/~nr/cs257/archive/david-roundy/Theo...
luckydude mentioned real per-file history for example¹, and that pushed me to remember per-file comments as the thing I'd want back.
Perhaps someone is listening.
The original 1986 CVS¹ is quite interesting from a historical prospective. Given that the implementation is just a bunch of scripts on top of RCS you can see how it plumbed together really easily.
There is a note¹ on Grune's site, that explains the relationship between the scripts and the system people would more likely recognise as CVS(assuming you're old enough to recognise it at all).
¹ https://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/usenet/...
² https://dickgrune.com/Programs/CVS.orig/CVS_BB_and_GNU
Edit: And I guess you might not recognise the archives in the first footnote either. They're shar files which can be extracted using the files as a script or more simply with unshar from sharutils³.
It had left me wondering what had caused it. There was a thread a few weeks ago where the old guard were describing an actual attempt to game the system, and I wondered if we were seeing a version of that being played out.
Was the conference recorded? I've tried searching, but I'm not turning anything up.
As an outsider you get my worthless full agreement on strictness of history, and on solving the monorepo or vendoring dilemmas. My employer at the time of the upheaval was a bitmover customer, and as we slowly switched away one repo at a time it definitely felt like a sideways step. I'd hesitate to say backwards because it did come with some big process improvements for us, but definitely not forwards.
I'd surely have been proud of solving problems with the quality that BK did too. I remember playing with a lot of the open source systems of the time¹, and none of them were in the same league. I'll make no apologies for this sounding like truly weird fan mail.
¹ I'm remembering hg, darcs, monotone, $some_implementation_of_arch, prcs, codeville but there was a lot of people in the space to some degree.
I can't be the only one who'd be interested in your views on the general developments for such important tools of our trade. Have you written about it anywhere? I'll pre-order "Larry walks us from SCCS to the git monoculture".
The response here makes me think there are others who like the idea though, so I'll try to float it in the local CC forum.
I'm kind of aware of Keirin from watching track, but wasn't aware of the depth in the local market. That Chris Hoy video was great, thanks!
Part of me wants to see all the new advancements, but I also hate it when it ruins an otherwise good spectacle or personal ride.
We also saw it with e-shifting in road, but that seems to have largely been solved. So, perhaps any problems that should arise with this could be shaken out in a couple of seasons too? </fence>
Maybe there is a market for racing and events where you're only allowed steel-framed, canti brakes, SiS index shift monstrosities? Like one of those sub-$1k car rallies or something.
I'm not sure whether I'd move the actual branching in because of the balancing issue, that is point where my hairs stand up. Perhaps, this is where it all falls apart.
zargs -P $(nproc) -i ***(#i).(pdf|azw3) -- calibre-convert \{\} \{\}.epub
We're firing up nproc tasks, matching case-insensitive .pdf or and .azw3 at any depth, and then batch processing them. zargs is documented in zshcontrib(1).It doesn't feel that different to your imagined syntax to me, quite whether that matches your mental model better is for you to decide though.
For example, from my Wikipedia trail I see Maurice Nivat come up in the adviser camp for a few of the more current names.
nnn() {
declare -x +g NNN_TMPFILE=$(mktemp --tmpdir $0.XXXX)
trap "rm -f $NNN_TMPFILE" EXIT
=nnn $@
[ -s $NNN_TMPFILE ] && source $NNN_TMPFILE
}
You can use a static file if you're sure you'll never be running more than one instance.I'd prefer something like:
nnn() {
local tmp=$(mktemp --tmpdir $0.XXXX)
trap "rm -f $tmp" EXIT
=nnn -p $tmp $@
[ -s $tmp ] && cd ${"$(< $tmp)":h}
}
That will cd to the selected file's directory with enter/right, or do nothing if you simply quit. I guess it depends if you use it for browsing a lot or simply picking a file.> The following is a list of all the standard widgets, and their default bindings in emacs mode, vi command mode and vi insert mode (the `emacs', `vicmd' and `viins' keymaps, respectively).
What that means is that if you issue 'bindkey -e' from a bare .zshrc it will enable the emacs bindings and C-q will work. The other two unbound entries state that it isn't enabled by default if you want to use vi-style editing.
The KEYMAPS section in the man page has a full explanation. The easy way to play with it is to start an extra zsh with "zsh -f" so it ignores your configs, call "bindkey" to see what the default bindings are like, then "bindkey -e; bindkey" to see all the goodies that are enabled in emacs mode for example.
Edit: Thanks for responses. And a warning to others: don't start following links to advisers and students in Wikipedia, it never finishes.
Just south of Cambridge is the intersection between Icknield Way¹ and Ermine Street², and you hardly seem to be able to stick a trowel in the ground without finding a coin hoard in these parts. You can still walk large parts of it on footpaths and bridleways. Not as pretty as Wales, but nice nonetheless.
I'll also add a reminder to check back here in a few days to see how you've fared :)
Hmm, I'd never considered that. I keep seeing people talking about buying really expensive 90s Sony TVs for retro gaming or resorting to iffy display filters in their emulator, but a clip-on lens could be nice. And frankly, I'm not sure my desk or tables would support one of those 90s monsters anyway.
I'm imagining one of those odd "anti-radiation filters" that were all the rage in the CRT days. Have to remember to check back in a few days to see if any commenters there have posted a workable home solution.
There are a bunch of other search types available, zshzle(1) has all the gory details.
To that point zsh has some excellent additions for process substitution beyond bash's <(list), but it also makes for yet more weird incompatibilities for when that matters. I only looked at this to start with because I assumed the space was because =() would have been treated as the full path modifier for a command called (), because it would mean that with any other character including other bracket types. TIL.
zsh does have the emulate builtin available to help with some basic things, but it is still easy to produce scripts littered with zsh'isms.
However, I do use zsh for personal scripts. In fact, I go so heavy on zsh'isms I know I'd need to rewrite things to share them if non-zsh users are an issue. It is easier to keep track of things that way, instead of tripping over the little easily forgotten quirks.
https://zdharma.org/Zsh-100-Commits-Club/Zsh-Native-Scriptin...