All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Wolfram Sang <wsa@kernel.org>, cocci@inria.fr
Subject: Re: [cocci] new version 1.2
Date: Tue, 16 Apr 2024 14:15:48 +0200 (CEST)	[thread overview]
Message-ID: <fa25ff69-acf1-baa0-31f-936116b3cc57@inria.fr> (raw)
In-Reply-To: <cdn5ct3pmn3l4yuohu6ulfndv7iy3pl5ycrdgxrgrqnd6czijn@tmoibbjtofa7>



On Fri, 12 Apr 2024, Wolfram Sang wrote:

>
> > I don't see this problem.  I made a silly semantic patch, wet-ul_l.cocci:
>
> My gut feeling was correct. I use CDPATH (bash feature). If I unset
> CDPATH, everything works as you said. I use 'CDPATH=.:<my_home_dir>' but
> setting CDPATH to '.' alone will expose the issue already.
>
> I can unset CDPATH in my scripts as a workaround. Dunno if you have time
> to work on a fix. I also don't see how CDPATH affects iterating through
> a directory. Sadly, I can't read OCaml.
>
> Thank you for your help, Julia!

I can just try it, but what is CDPATH for?

julia

  reply	other threads:[~2024-04-16 12:15 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 [this message]
2024-04-16 12:23                 ` Wolfram Sang
2024-04-16 16:07                   ` Julia Lawall
2024-04-16 19:29                     ` Wolfram Sang
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=fa25ff69-acf1-baa0-31f-936116b3cc57@inria.fr \
    --to=julia.lawall@inria.fr \
    --cc=cocci@inria.fr \
    --cc=wsa+renesas@sang-engineering.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.