From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: off topic
Date: Fri, 09 Dec 2016 19:31:06 -0800 [thread overview]
Message-ID: <584B76FA.8030403@eastlink.ca> (raw)
In-Reply-To: <95362.1481338226@hydra.kiddle.eu>
On 12/09/2016 06:50 PM, Oliver Kiddle wrote:
> Rather than a source-able file, would it perhaps make sense to embrace
> the concept of plugins. It's a concept that people are familiar with
> from other software.
> And if we've kept
> things simple,
Please ;-)
> it could work to just source a single file for a
> plugin.
>
> Finally, we could include the odd plugin in the distribution for
> anything which could be considered fairly core - such as the sensible
> defaults plugin.
The cool thing is just the concept that one can plug something in to try
it then unplug it later. I'm sure I'm not the only dude who's changed
something, busted it, and not known exactly how to back out of it.
Coolest if there's no extra tech involved at all and it's just a way of
conceptualizing that some script or other is a system modifier set up in
such a way that plugging it out is as easy as plugging it in and with
the culture that there's several options one might want to try.
Somewhere there is a file full of prompt ideas, nicely labeled:
'Oliver's prompt' 'Bart's prompt', etc. and it invites you to try them
and find the one you like -- sorta like that. Could have a dozen nicely
named potential configuration plugins -- try one, try 'em all. Probably
mostly just alternate zshrc's really but it's how you present it.
Labeled a plugin, we have the paradigm already. Mind, there could be
some hugely useful extra tech too, easy to understand, intuitive,
tractable, robust ... all the things that shell writers hate ;-))
next prev parent reply other threads:[~2016-12-10 3:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161209130109epcas2p1fd786d46827852a8cf1badcb5d003ec9@epcas2p1.samsung.com>
2016-12-09 12:29 ` vi mode reset Christian Brabandt
2016-12-09 14:33 ` Ray Andrews
2016-12-09 14:41 ` Peter Stephenson
2016-12-09 14:44 ` Oliver Kiddle
2016-12-09 15:07 ` off topic Ray Andrews
2016-12-09 16:28 ` Oliver Kiddle
2016-12-09 17:45 ` Ray Andrews
2016-12-10 0:54 ` Bart Schaefer
2016-12-10 2:50 ` Oliver Kiddle
2016-12-10 3:13 ` Bart Schaefer
2016-12-10 3:31 ` Ray Andrews [this message]
[not found] ` <95362.1481338226__15466.9970310808$1481338718$gmane$org@hydra.kiddle.eu>
2016-12-11 4:32 ` Daniel Shahaf
2016-12-11 17:07 ` Ray Andrews
2016-12-11 17:19 ` Bart Schaefer
2016-12-11 18:02 ` Ray Andrews
2016-12-11 19:20 ` Bart Schaefer
2016-12-11 20:23 ` Ray Andrews
[not found] ` <584AEDBF.2050402__19991.0537027337$1481307418$gmane$org@eastlink.ca>
2016-12-09 19:24 ` Daniel Shahaf
2016-12-09 20:25 ` Ray Andrews
[not found] ` <584B1325.1010907__10266.7204490446$1481316980$gmane$org@eastlink.ca>
2016-12-10 0:14 ` Daniel Shahaf
2016-12-10 0:21 ` Ray Andrews
2016-12-12 13:11 ` Vincent Lefevre
2016-12-09 15:48 ` vi mode reset Christian Brabandt
2016-12-09 16:46 ` Oliver Kiddle
2016-12-09 20:24 ` Christian Brabandt
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=584B76FA.8030403@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).