public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [Attn: base-files maintainer] Changing /etc/profile to add more shell-dependent settings
Date: Wed, 14 Oct 2015 20:15:00 -0000	[thread overview]
Message-ID: <87h9ltqk94.fsf@Rainer.invalid> (raw)
In-Reply-To: <20151014171400.GP14466@dinwoodie.org> (Adam Dinwoodie's message	of "Wed, 14 Oct 2015 18:14:00 +0100")

Adam Dinwoodie writes:
> The only other option I can think of is to rename the .bash file to .sh
> and to patch it to check $BASH_VERSION before running the Bash-specific
> code.  That seems fragile though -- it means putting Bashisms in a
> script that may be run by non-Bash shells (even if it's gated by
> checking $BASH_VERSION), and it means a patch of the upstream fzf Bash
> script in a way that's essentially just duplicating code already in
> /etc/profile.

Sourcing that script would actually belong into /etc/bash.bashrc if I
understand correctly what this is supposed to do.  Unfortunaltely there
is no infrastructure set up to do this yet in bash.bashrc and simply
changing the file makes it non-upgradeable.  OTOH what I see there on my
Linux system is far too complicated for Cygwin, I'll have to think about
this some more.

> (The upstream solution to this is to add code to the user's ~/.bashrc to
> source the relevant scripts, but I don't think that's feasible when
> installing the scripts via setup-*.exe.)

No, that should indeed be left to the user.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      parent reply	other threads:[~2015-10-14 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 15:53 Adam Dinwoodie
2015-10-14 16:20 ` Andrey Repin
2015-10-14 16:20 ` Yaakov Selkowitz
2015-10-14 16:32   ` Adam Dinwoodie
2015-10-14 16:53 ` Achim Gratz
2015-10-14 17:14   ` Adam Dinwoodie
2015-10-14 18:35     ` Andrey Repin
2015-10-14 18:49       ` Adam Dinwoodie
2015-10-14 20:15     ` Achim Gratz [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=87h9ltqk94.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).