From: "Rudolf Adamkovič" <salutis@me.com>
To: emacs-orgmode@gnu.org
Subject: URL woes that never end
Date: Wed, 16 Jun 2021 00:52:04 +0200 [thread overview]
Message-ID: <m2k0muzqp7.fsf@me.com> (raw)
Greetings!
I lamented a while ago about URL handling in Org. To provide a concrete example, below is a shell script that Org does not export correctly to HTML. More specifically, Org considers the script to be a URL. Further, and amazingly, even if I change “see <URL>.” to “see <URL> to learn more”, Org *still* does not parse the URL correctly, even with a valid URL per RFC *and* surrounding angle brackets (<>) *and* spaces on both sides.
#+begin_src shell :tangle fetchmail-retry.sh :shebang #!/usr/bin/env sh
# fetchmail-retry.sh -- fetchmail with retry
#
# Author: Rudolf Adamkovič <salutis@me.com>
# Version: 1.0
#
# This file is free software: you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by the
# Free Software Foundation, either version 3 of the License, or (at
# your option) any later version.
#
# For more information, see <http://www.gnu.org/licenses/>.
#
RETRY=0
RETRY_MAX=10
RETURN_OK=0
RETURN_NO_MAIL=1
while [ $RETRY -le $RETRY_MAX ]
do
fetchmail "$@"
RETURN=$?
[ $RETURN -eq $RETURN_OK ] && exit $RETURN
[ $RETURN -eq $RETURN_NO_MAIL ] && exit $RETURN
RETRY=$((RETRY+1))
echo Retry \#$RETRY:
done
echo Failed after $RETRY_MAX retries. >&2
exit $RETURN
#+end_src
--
Logic is a science of the necessary laws of thought, without which no employment of the understanding and the reason takes place. -- Immanuel Kant, 1785
Rudolf Adamkovič <salutis@me.com>
Studenohorská 25
84103 Bratislava
Slovakia
[he/him]
next reply other threads:[~2021-06-15 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 22:52 Rudolf Adamkovič [this message]
2021-06-16 13:16 ` URL woes that never end Nicolas Goaziou
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=m2k0muzqp7.fsf@me.com \
--to=salutis@me.com \
--cc=emacs-orgmode@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.
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).