From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: [Attn. Maintainer] /etc/profile.d/lapack0.csh
Date: Sun, 02 Jun 2019 15:37:00 -0000 [thread overview]
Message-ID: <87woi4yp5k.fsf@Rainer.invalid> (raw)
The profile script for csh does not work as intended. Since it must be
sourced, it leaves variables set in the user shell and potentially
clobbers variables the user might use ($newpath is just too obvious a
name). Something like this should be more robust:
--8<---------------cut here---------------start------------->8---
set __LA_BINDIR=/usr/lib/lapack
set __LA_PATH=($path:q $__LA_BINDIR:q)
foreach __LA_F ($path:q)
if ( "$__LA_F" == "$__LA_BINDIR" ) then
set __LA_PATH=($path:q)
break
endif
end
set path=($__LA_PATH:q)
unset __LA_*
--8<---------------cut here---------------end--------------->8---
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next reply other threads:[~2019-06-02 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 15:37 Achim Gratz [this message]
2019-06-04 7:38 ` Marco Atzeri
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=87woi4yp5k.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).