From: Carsten Dominik <dominik@science.uva.nl>
To: Scott Otterson <scotto@u.washington.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: shell links [was: Version 4.19c]
Date: Thu, 6 Apr 2006 21:28:19 +0200 [thread overview]
Message-ID: <99190467852be4837e9eae9cc2f4f95d@science.uva.nl> (raw)
In-Reply-To: <44354222.60104@u.washington.edu>
> Lot's of nice changes in 4.19. I'm really impressed at how fast
> Carsten & Co. are cranking out new code and new fixes.
Fixing goes fast if people are out there testing things. Thanks for
your report.
>
> Looks like there are a few problems with shell links in 4.19c, though.
>
> 1.) If I type C-c C-l, and then at the link: prompt, type
>
> shell:SPACE
>
> where SPACE means I hit the spacebar, then I get a [No Match] error
> message. If I instead type:
>
> shell:lsSPACE
>
> then I get the [No Match] error after the 'ls'
This is because SPACE does completion in the minibuffer. Hmm. Ok, I
can turn this default off and make SPACE insert itself. This means
that only TAB will do completion in the minibuffer at the C-c C-l
prompt. Not a problem, I guess.
>
> 2.) If I manually make a shell link like this
>
> [[shell:ls *.org][shellcmd]]
>
> and then type C-c C-o. The minibuffer asks m:
>
> Execute " " in the shel? (yes or no)
>
> Even though there's a blank, the ls command works if I say yes
The command is there, it is only invisible because it is a copy of the
invisible command in the [[ ]] link :-). I am removing this
invisibility property now.
>
> 3.) If I put the cursor in the link and type C-c C-l, then
> the minibuffer says:
>
> Link: shell:ls%20*.org
>
> If I cancel (C-g), C-c C-o still works.
>
In the hidden part of a link, space and brackets are escaped. I forgot
to unescape for the editing prompt.
While I was at it, I have also removed the restrictions on shell
commands. Shell: links in [[ ]] brackets can now contain "<", ">", and
"|". These restrictions were only needed in <> links, but now no
longer. This is nice.
Also, maybe you'd like to know that there is a variable to turn off the
safety query in shell links: org-confirm-shell-links. I could also
change the yes-or-no query to a y-or-n query to make it easier to
answer.... We'll see, not now.
> Scott
Thanks. The above named changes are in
http://www.astro.uva.nl/~dominik/Tools/org/org-4.19d.zip
- Carsten
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
next prev parent reply other threads:[~2006-04-06 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 16:30 shell links [was: Version 4.19c] Scott Otterson
2006-04-06 19:28 ` Carsten Dominik [this message]
2006-04-10 17:41 ` Scott Otterson
2006-04-11 11:47 ` Carsten Dominik
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99190467852be4837e9eae9cc2f4f95d@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=scotto@u.washington.edu \
/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.savannah.gnu.org/cgit/emacs/org-mode.git
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).