From: bokr@bokr.com
To: Csepp <raingloom@riseup.net>
Cc: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
61882@debbugs.gnu.org
Subject: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues
Date: Wed, 1 Mar 2023 15:40:28 +0100 [thread overview]
Message-ID: <20230301144027.GA37832@LionPure> (raw)
In-Reply-To: <87ilfklns5.fsf@riseup.net>
Hi,
On +2023-03-01 12:16:56 +0100, Csepp wrote:
[...]
> How the hell would my paths affect what's in the bin folder? Like, the
> flatpak binary is literally not present in the profile, that's why it's
> not showing up in $PATH.
Could something in one of your path directories
accidentally have gotten a name starting with '-' ?
(or full name '-')?
Surprising things can happen depending on how an
app rejects an unexpected option, or tries to use it :)
BTW: If you can't delete a file named '-'
try emacs dirmode. IIRC emacs seems to see
anything and be able to delete it.
Do you have any scripts that are both sourced and executed?
If so, are they doing return or exit respectively or
something trickier as intended?
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2023-03-01 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 2:58 bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Csepp
2023-03-01 9:25 ` Liliana Marie Prikler
2023-03-01 11:16 ` Csepp
2023-03-01 14:40 ` bokr [this message]
2023-03-01 16:11 ` Csepp
2023-03-02 7:11 ` Liliana Marie Prikler
2023-03-02 12:39 ` Csepp
[not found] ` <handler.61882.B.167763983720587.ack@debbugs.gnu.org>
2023-04-06 14:59 ` bug#61882: profile is frozen / packages can't be installed Csepp
2023-10-04 2:54 ` bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Maxim Cournoyer
2023-10-08 14:29 ` Csepp
2023-10-08 20:51 ` Maxim Cournoyer
2023-10-10 22:52 ` Csepp
2023-10-11 1:47 ` Maxim Cournoyer
2023-10-15 20:06 ` Csepp
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=20230301144027.GA37832@LionPure \
--to=bokr@bokr.com \
--cc=61882@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=raingloom@riseup.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.