From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: commas in URLs?
Date: Thu, 31 Jan 2008 18:22:20 +0000 [thread overview]
Message-ID: <20080131182220.GF21213@atlantic.linksys.moosehall> (raw)
In-Reply-To: <878x25lws8.fsf@bzg.ath.cx>
On Thu, Jan 31, 2008 at 06:39:19PM +0100, Bastien wrote:
> Carsten Dominik <dominik@science.uva.nl> writes:
> >> On Thu, Jan 31, 2008 at 06:43:25AM +0100, Carsten Dominik wrote:
> >>> Yes, plain links are terminated by (among other) comma.
> >>>
> >>> Please enclose such links into <...> or [[...]]]
> >>
> >> Ah, OK thanks! Just curious - what's the reasoning behind excluding
> >> commas?
> >
> > So that you can write
> >
> > Popular search engines are http://google.com, http://yahoo.com, and
> > http://ask.com
>
> So URLs should just exclude commas that are followed by a whitespace or
> a line break, not all commas - right?
Hmm, good point!
> Anyway, I guess 99% of URLs are enclosed in brackets,
Not true here, by a long shot!
$ egrep -c 'https?://' */TODO.org
work/TODO.org:78
personal/TODO.org:180
$ egrep -c '[<[]https?://' */TODO.org
work/TODO.org:8
personal/TODO.org:50
So that's 58 out of 258 enclosed in brackets, which is 22.5%.
> so it might not be worth being fussy on this...
s/not be// ;-)
next prev parent reply other threads:[~2008-01-31 18:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 18:53 commas in URLs? Adam Spiers
2008-01-31 5:43 ` Carsten Dominik
2008-01-31 14:46 ` Adam Spiers
2008-01-31 14:59 ` Carsten Dominik
2008-01-31 16:29 ` Adam Spiers
2008-01-31 17:39 ` Bastien
2008-01-31 18:22 ` Adam Spiers [this message]
2008-01-31 18:34 ` Carsten Dominik
2008-01-31 23:16 ` Leo
2008-01-31 23:43 ` Adam Spiers
2008-01-31 23:59 ` Leo
2008-02-01 0:40 ` Adam Spiers
2008-02-01 8:58 ` Phil Jackson
2008-02-01 15:09 ` Piotr Zielinski
2008-02-01 22:31 ` 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=20080131182220.GF21213@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.org \
--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).