emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Denis Bitouzé" <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]
Date: Tue, 22 Sep 2015 21:56:09 +0200	[thread overview]
Message-ID: <m3io721b52.fsf@example.com> (raw)
In-Reply-To: <8737y6b5v4.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> (Nicolas Goaziou's message of "Tue, 22 Sep 2015 21:39:59 +0200")

Le 22/09/15 à 21h39, Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> a écrit :

> Hello,

Hello,

>> As you can see, the anchor in the .md file is at the end of the header and, in
>> case this header contains long text, clicking on a link to this anchor would
>> lead us to the end, eventually not at the first line, of this header.
>
> True. But there's a trade-off: putting anchor at the beginning of the
> heading is less readable.

I don't see your point.

1. What is less readable: the anchor or, if the anchor is at its
   beginning, the heading ?
2. At what level is it less readable: .org or .md or .html, etc.?

Regards,
-- 
Denis

  parent reply	other threads:[~2015-09-22 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 19:59 Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)] Denis Bitouzé
2015-09-22 19:39 ` Nicolas Goaziou
     [not found]   ` <8737y6b5v4.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-22 19:56     ` Denis Bitouzé [this message]
2015-09-22 20:01       ` Nicolas Goaziou
     [not found]         ` <87vbb29qay.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-22 20:11           ` Denis Bitouzé

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=m3io721b52.fsf@example.com \
    --to=dbitouze-39zsbgiqgt5gwvitb5qawa@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).