From: "John O'Meara" <john.fr.omeara@gmail.com>
To: Laurent Bercot <ska-skaware@skarnet.org>
Cc: "skaware@list.skarnet.org" <skaware@list.skarnet.org>,
"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: [announce] execline-2.5.0.0
Date: Mon, 02 Apr 2018 12:12:35 +0000 [thread overview]
Message-ID: <CAPCpfp80yX_9=kNHSpxcw-SwKt3q0FH0D2j3O6sNCrLi6NTctA@mail.gmail.com> (raw)
In-Reply-To: <CAPCpfp-abfPEz24FCr7UUKup5NH+DLsw8FhW5KMA9Tuo2TMrBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2336 bytes --]
heh, only now did I realize the date of the past
On Mon, Apr 2, 2018, 8:07 AM John O'Meara <john.fr.omeara@gmail.com> wrote:
>
>
> On Mon, Apr 2, 2018, 8:06 AM John O'Meara <john.fr.omeara@gmail.com>
> wrote:
>
>> While I initially didn't like the 2.4 name changes, perhaps I (and
>> others) just need tinge to get used too it.
>
>
> that should have been "time", not "tinge". The perils of writing email on
> a phone :-(
>
> Perhaps it would be useful to have a period of time where the old names
>> are used for the programs and the new names are symlinks to the old names?
>> Existing scripts would still work while we experiment with the new naming
>> convention.
>>
>> --
>> John O'Meara
>>
>>
>> On Mon, Apr 2, 2018, 6:39 AM Laurent Bercot <ska-skaware@skarnet.org>
>> wrote:
>>
>>>
>>> Hello,
>>> execline-2.5.0.0 is out.
>>>
>>> It is with a very heavy heart that I must do this release.
>>> User reports have come in by the hundreds and they are almost
>>> unanimous (sorry, Colin): they don't like the 2.4.0.0 change,
>>> pretending it hurts readability (as if), and writability too,
>>> of execline scripts. (What? People were actually writing execline
>>> scripts? Why haven't I heard of them before yesterday?)
>>> They want a revert to the old syntax.
>>>
>>> Users. They never know what they want. They can't be happy. Give them
>>> what they ask for and they immediately start complaining about the
>>> opposite of what they were complaining before. They're a plague on
>>> software authors everywhere. I swear, computer programming would be
>>> so much easier if there were no users at all!
>>>
>>> But since programming is about being a slave to your users, I hear
>>> them, and I submit. I'm reverting the change introduced in 2.4.0.0.
>>> execline commands will keep the names they had in 2.3.0.4 and previous
>>> versions.
>>>
>>> I'm such a misunderstood genius.
>>>
>>> The main difference between 2.3.0.4 and 2.5.0.0, though, is that
>>> the "import" command has been removed. From 2.5.0.0 on, execline and
>>> ImageMagick should not conflict anymore. Make sure your execline
>>> scripts have been converted to using "importas"!
>>>
>>> https://skarnet.org/software/execline/
>>> git://git.skarnet.org/execline
>>>
>>> Enjoy,
>>> Bug-reports welcome.
>>>
>>> --
>>> Laurent
>>>
>>>
next prev parent reply other threads:[~2018-04-02 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 10:39 Laurent Bercot
2018-04-02 12:06 ` John O'Meara
[not found] ` <CAPCpfp9rp-N5nK5=darnBFH0BzZ0yKrrKiXdWZWtOcxGzDPE+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-02 12:07 ` John O'Meara
2018-04-02 12:12 ` John O'Meara [this message]
2018-04-02 12:13 ` Alex Efros
2018-04-02 16:56 ` Guillermo
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='CAPCpfp80yX_9=kNHSpxcw-SwKt3q0FH0D2j3O6sNCrLi6NTctA@mail.gmail.com' \
--to=john.fr.omeara@gmail.com \
--cc=ska-skaware@skarnet.org \
--cc=skaware@list.skarnet.org \
--cc=supervision@list.skarnet.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.
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).