From: "Alexander Duscheleit" <alexander.duscheleit@sweevo.net>
To: zsh-workers@zsh.org
Subject: Problem with VCS_info in nested nfs mounts
Date: Sun, 08 Oct 2023 15:59:44 +0000 [thread overview]
Message-ID: <ff16b4cd6712e9b9714718f3a55a809f1a50c047@sweevo.net> (raw)
Hi all,
I first posted this problem at https://github.com/grml/grml-etc-core/issues/141 but got no reply.
Upon further investigation, the gmrl vcs prompt relies heavily on the VCS_info module, so the culprit may lie there.
When I cd into a deeply nested NFS mount the current path is somehow broken via the VCS module.
[root@client] ~ # showmount -e server
Export list for server:
/mnt/storage/share/Pictures 192.168.0.99
/mnt/storage/share/Programs 192.168.0.99
/mnt/storage/share/Downloads 192.168.0.99
/mnt/storage/share/Books 192.168.0.99
/mnt/storage/share/Clips 192.168.0.99
/mnt/storage/share/Music 192.168.0.99
/mnt/storage 192.168.0.99
(The nested exports are because those are BTRFS subvolumes which require manually setting fsids)
[root@client] ~ # cd /mnt/server/share/Music/X-Mas
[root@client] /mnt/server/share/Music/X-Mas # /bin/ls
bin boot checkout dev esp etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var
[root@client] /mnt/server/share/Music/X-Mas # /bin/ls $PWD
'Die Stars Der Hitparade Feiern Weihnachten (2009)' 'RTL Weihnachten 2008' 'The Ultimate Christmas Music Collection'
'Various Artists' 'Frank Schöbel' 'Roland Kaiser'
'Top Christmas Songs of All Time' 'von Wilfried'
You can clearly see the difference between `ls` and `ls $PWD`, which should not exist.
Removing the VCS module from `:prompt:grml:left:setup` fixes this.
I'm not that familiar with zsh configuration, so if someone could supply a minimal .zshrc employing plain VCS_info I would be prepared to test that.
Thanks,
Alex
P.S.: I'm not subscribed to the list, so please CC all inquiries.
reply other threads:[~2023-10-08 18:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ff16b4cd6712e9b9714718f3a55a809f1a50c047@sweevo.net \
--to=alexander.duscheleit@sweevo.net \
--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).