From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Roland Winkler" <winkler@gnu.org>
Subject: bug#13668: 24.2.93; strike-through in org mode
Date: Sun, 10 Feb 2013 11:08:03 -0600
Message-ID: <20759.54259.751629.173184@gargle.gargle.HOWL>
References: <87fw153vsd.fsf@gnu.org> <87halkn6bz.fsf@bzg.ath.cx>
	<20759.39415.151607.366601@gargle.gargle.HOWL>
	<87zjzc2kxx.fsf@bzg.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:42922)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1U4aOY-0008NW-Jt
	for emacs-orgmode@gnu.org; Sun, 10 Feb 2013 12:08:53 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1U4aOV-0005IA-5G
	for emacs-orgmode@gnu.org; Sun, 10 Feb 2013 12:08:50 -0500
Sender: debbugs-submit-bounces@debbugs.gnu.org
Resent-Message-ID: <handler.13668.B13668.136051610829028@debbugs.gnu.org>
In-Reply-To: <87zjzc2kxx.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@altern.org>
Cc: 13668@debbugs.gnu.org

On Sun Feb 10 2013 Bastien wrote:
> > Why put this in a separate FAQ? Aren't the info pages the first
> > source of information for such things?
> 
> Depends.  We try to keep the info manual readable, and it's already
> quite long.  If you can find a good place in the manual, please send
> a patch.

I do not find the info nodes on "Structural markup elements"
particularly overloaded. The node "Emphasis and monospace" is just
one short paragraph, and org-fontify-emphasized-text could esily be
mentioned there -- unless this variable also affects other things,
so that it should be mentioned higher up in the node hierarchy.

If such things get distributed among different places, an info
manual plus a separate FAQ, they get yet more confusing, in
particular for casual users of org mode. Many users will not even
know (or expect) that the info manual does not give them the full
story, but they need to consult other sources, too.

Take the elisp manual: it's pretty big. But I like it because its
authors are pretty good in making it an *efficient* and *reliable*
source of information. (Here I'd like to put these words in bold,
because I really appreciate this!)