From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: Wrong expansion of ~/
Date: Thu, 27 Aug 2020 10:54:43 -0700 [thread overview]
Message-ID: <1ec59d9c-ec7a-ba93-d532-c9a2c29c2c87@jhmg.net> (raw)
In-Reply-To: <CA+7cx1oz0w7L4xmYVn-M5kUQQcLzy90qpM22t7S-1K=RGome0g@mail.gmail.com>
On 8/27/2020 12:44 AM, Morten Kjærulff via Cygwin wrote:
> On Tue, Aug 25, 2020 at 3:00 PM Brian Inglis wrote:
>>
>> On 2020-08-25 01:15, Morten Kjærulff via Cygwin wrote:
>>> On Mon, Aug 24, 2020 at 10:41 PM Brian Inglis wrote:
>>>>
>>>> On 2020-08-24 06:36, Morten Kjærulff via Cygwin wrote:
>>>>> On Mon, Aug 24, 2020 at 11:52 AM Thomas Wolff wrote:
>>>>>> Am 24.08.2020 um 10:05 schrieb Morten Kjærulff via Cygwin:
>>>>>>> I have a script that starts several tmux panes with my favorite commands.
>>>>>>> In some (*some* and only *sometimes*) of the panes I see:
>>>>>>>
>>>>>>> -bash: /home/xxxxxP/.git-completion.bash: No such file or directory
>>>>>>> -bash: /home/xxxxxP/.git-prompt.sh: No such file or directory
[snip]
> I really don't know how I can debug this?
>
> With this:
>
> . ~/.git-completion.bash
>
> ~ is *sometimes* expanded wrongly:
>
> With this:
>
> while [ ! ~ = $HOME ] ; do
> echo "$0: !!! ~ =! \$HOME" >&2
> done
> . ~/.git-completion.bash
>
> I *sometimes* see an endless loop.
>
> With this:
>
> while [ ! ~ = $HOME ] ; do
> echo "$0: !!! ~ =! \$HOME" ~ $HOME >&2
> done
> . ~/.git-completion.bash
>
> I see no error.
>
> I have a script that I run under mintty. The script starts tmux, with
> some panes. I see the error *sometimes* in *some* panes (not the same
> every time).
What happens if you use $HOME instead of ~ ?
--
Jim Garrison jhg@acm.org
prev parent reply other threads:[~2020-08-27 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 8:05 Morten Kjærulff
2020-08-24 9:50 ` Thomas Wolff
2020-08-24 12:36 ` Morten Kjærulff
2020-08-24 20:39 ` Brian Inglis
2020-08-25 7:15 ` Morten Kjærulff
2020-08-25 12:58 ` Brian Inglis
2020-08-27 7:44 ` Morten Kjærulff
2020-08-27 16:49 ` rifter
2020-08-27 17:56 ` Thomas Wolff
2020-08-28 6:29 ` Morten Kjærulff
2020-08-27 17:54 ` Jim Garrison [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=1ec59d9c-ec7a-ba93-d532-c9a2c29c2c87@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.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 read-only IMAP folder(s) and NNTP newsgroup(s).