zsh-workers
 help / color / mirror / code / Atom feed
From: Elias Ghafari <eliasghafari@disroot.org>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Oliver Kiddle <opk@zsh.org>, zsh-workers@zsh.org
Subject: Re: [BUG]Filename autocompletion using git-bare repos (--git-dir=... --work-tree=...)
Date: Mon, 11 Sep 2023 18:05:01 +0300	[thread overview]
Message-ID: <sbqxnmygbilnzlni4jh3nneermjldjs6a3ly23cstw56wuoxud@wk4aht2p5irl> (raw)
In-Reply-To: <CAN=4vMoqiFcB_dXZZ9SzX826SC6bT+p5SMdjbva=ah5bGSq-xQ@mail.gmail.com>

On 23/03/10 11:12AM, Roman Perepelitsa wrote:
> You can either replace `--work-tree=~` with `--work-tree ~` or set
> magic_equal_subst. I'd do the former.

Hello again,

This solution worked perfectly until a month or so ago, but then it
stopped working.
I still use the same alias:
config='git --git-dir=$HOME/.local/share/dotfiles --work-tree ~' 

I don't know what has changed but $HOME is not expanding and executing
`zsh 2>log` returns this after trying `config diff <Tab>`:
fatal: not a git repository: '$HOME/.local/share/dotfiles'

Which is weird this error happened the last time on git's side saying
that '~/.local/share/dotfiles' is not a git repo when I replaced $HOME
with ~. But as you can see this resulted from Zsh.
Any idea of what has changed to cause this, and if this can be solved ?

Thanks,
Elias.


  reply	other threads:[~2023-09-11 15:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 12:33 eliasghafari
2023-03-09 17:12 ` Bart Schaefer
2023-03-09 19:27 ` Oliver Kiddle
2023-03-09 23:54   ` The (e) parameter flag and side-effects Bart Schaefer
2023-03-10 10:07   ` [BUG]Filename autocompletion using git-bare repos (--git-dir=... --work-tree=...) Elias Ghafari
2023-03-10 10:12     ` Roman Perepelitsa
2023-09-11 15:05       ` Elias Ghafari [this message]
2023-09-12  2:26         ` Jun T
2023-09-12  8:54 eliasghafari
2023-09-12  9:34 ` Roman Perepelitsa
2023-09-12 19:25   ` eliasghafari
2023-09-12 19:33     ` Roman Perepelitsa

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=sbqxnmygbilnzlni4jh3nneermjldjs6a3ly23cstw56wuoxud@wk4aht2p5irl \
    --to=eliasghafari@disroot.org \
    --cc=opk@zsh.org \
    --cc=roman.perepelitsa@gmail.com \
    --cc=zsh-workers@zsh.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).