From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Wolfram Sang <wsa@kernel.org>, cocci@inria.fr
Subject: Re: [cocci] new version 1.2
Date: Tue, 16 Apr 2024 21:29:42 +0200 [thread overview]
Message-ID: <ntvebql752m4fxp4whbpeuyqrg26gfoqo5tvzi7ouxxp2z5qrq@cpoe42jvto77> (raw)
In-Reply-To: <762b29b1-c2ba-e9e6-1054-5d4bf54b6843@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
> requires a cd to the specified directory. With the CDPATH variable set,
> cd to a relative path prints the full path of the destination to standard
> output. That is collected as part of the standard output of the command
Ah, that explains.
> I can redirect the output of cd to /dev/null.
Yep, I do this in my scripts as well.
And for all current/future users: Set CDPATH, but don't export it[1].
That would also have avoided the problem. I did this now :/
[1] https://mywiki.wooledge.org/BashPitfalls#pf48
Thank you, Julia!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-16 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 21:05 [cocci] new version 1.2 Julia Lawall
2024-03-28 21:33 ` Gustavo A. R. Silva
2024-03-29 7:14 ` [cocci] Version 1.2 released Markus Elfring
2024-03-29 10:33 ` Julia Lawall
2024-04-11 20:58 ` [cocci] new version 1.2 Wolfram Sang
2024-04-11 21:05 ` Julia Lawall
2024-04-12 6:29 ` Wolfram Sang
2024-04-12 6:33 ` Julia Lawall
2024-04-12 6:50 ` Wolfram Sang
2024-04-12 6:59 ` Julia Lawall
2024-04-12 8:23 ` Wolfram Sang
2024-04-12 10:42 ` Wolfram Sang
2024-04-16 12:15 ` Julia Lawall
2024-04-16 12:23 ` Wolfram Sang
2024-04-16 16:07 ` Julia Lawall
2024-04-16 19:29 ` Wolfram Sang [this message]
2024-05-03 14:16 ` Denis Efremov
2024-05-03 15:32 ` Julia Lawall
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=ntvebql752m4fxp4whbpeuyqrg26gfoqo5tvzi7ouxxp2z5qrq@cpoe42jvto77 \
--to=wsa+renesas@sang-engineering.com \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=wsa@kernel.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).