From: Gregor Zattler <telegraph@gmx.net>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: problems with some external org-mode shell links which make emacs stuck
Date: Thu, 01 Feb 2024 10:05:24 +0100 [thread overview]
Message-ID: <87cytgv9kb.fsf@no.lan> (raw)
Dear Emacs users, I use org-mode's external links to
establish ssh portforwarding to several servers, like
so:
[[shell:ssh -N -F /etc/ssh/ssh_config -L localport:hostname:hostport -p port user@server& # comment1][comment2]]
If I do C-c C-o (org-open-at-point) on such a link,
the ssh portforwarding command is executed
successfully, but:
1. I'm asked every time if I want to execute the
command. This is annoying, is there a possibility
to stop this?
2. Emacs then shows "Executing ssh -N ..." in the echo
area and while I still see the active cursor on the
link I'm not able to move the point or switch
between windows, till I hit C-g. (In a terminal
emulator under bash command returns successfully,
it's exit code is 0.)
The problem does not stem from the "# comment1"
part, since the same does not happen with this link:
[[shell:/usr/bin/echo hund & # hund][hund]]
Any idea what's happening here?
If I instead use an external link of type elisp,
like so:
[[elisp:(shell-command "ssh -N -F /etc/ssh/ssh_config -L 30001:xxxxxxxx:8006 -p 2220 xxxx@xxxxxxxxxx & # comment1")][comment2]]
Problems are the same. I also experimented with
start-process, but with even less success.
The value of sh-shell-file is "/bin/bash". This is on Debian/Bookworm.
Emacs : GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, cairo version 1.16.0)
of 2024-01-25
Package: Org mode version 9.7-pre (release_9.6.17-1091-gea5290 @ /home/grfz/src/org-mode/lisp/)
But this also happens with emacs 28.2 and -Q.
Thanks for pointers, Gregor
next reply other threads:[~2024-02-01 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 9:05 Gregor Zattler [this message]
2024-02-01 12:18 ` problems with some external org-mode shell links which make emacs stuck Bruno Barbier
2024-02-01 22:15 ` Gregor Zattler
2024-02-02 9:56 ` Bruno Barbier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cytgv9kb.fsf@no.lan \
--to=telegraph@gmx.net \
--cc=help-gnu-emacs@gnu.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).