From: Andrey Repin <anrdaemon@yandex.ru>
To: Adam Dinwoodie <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: minor error in skel/.bashrc
Date: Tue, 8 Mar 2022 11:28:33 +0300 [thread overview]
Message-ID: <1277951355.20220308112833@yandex.ru> (raw)
In-Reply-To: <20220305132522.uq4yfrvmnrn4szvf@lucy.dinwoodie.org>
Greetings, Adam Dinwoodie!
> On Sat, Mar 05, 2022 at 09:26:06AM +0300, lvm wrote:
>> The identical /etc/skel/.bashrc and /etc/defaults/etc/skel/.bashrc contain
>> the same line
>>
>> # export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups
Not a nitpick or anything, but I've found a slightly clearer technique on the internet:
export HISTCONTROL=${HISTCONTROL:+$HISTCONTROL:}ignoredups
>>
>> But HISTCONTROL values should be colon separated, not comma separated. This
>> line is commented out, but if someone like me tries to use it without much
>> thinking...
> Confirmed.
> Achim, I've attached a patch that should fix this, based on the tip of
> https://sourceware.org/git/cygwin-apps/base-files.git
--
With best regards,
Andrey Repin
Tuesday, March 8, 2022 11:14:29
Sorry for my terrible english...
prev parent reply other threads:[~2022-03-08 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 6:26 lvm
2022-03-05 13:25 ` Adam Dinwoodie
2022-03-08 8:28 ` Andrey Repin [this message]
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=1277951355.20220308112833@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).