all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bastien <bastienguerry@googlemail.com>
To: Ulf Stegemann <ulf-news@zeitform.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [BUG] HTML exporting numbered literal examples
Date: Fri, 17 Jul 2009 16:50:18 +0200	[thread overview]
Message-ID: <87y6qn9xed.fsf@bzg.ath.cx> (raw)
In-Reply-To: <zf.upnskgvr55s.fsf@zeitform.de> (Ulf Stegemann's message of "Fri, 17 Jul 2009 12:10:39 +0200")

Ulf Stegemann <ulf-news@zeitform.de> writes:

> I think, those examples are easy to make up.  Line numbers are great for
> file contents and maybe input /or/ output.  But as soon as in- and output
> are mixed up I find them rather disturbing (imagine e.g. a shell
> session).  On the other hand removing labels and having that nice
> highlighting feature with HTML exported files maybe useful in either
> case.

I understand...

> I had a quick look at `org-export-number-lines' and the following seems
> to work smoothly ...

Thanks for the patch.  One problem though: now the first link (from the
manuals example) looks like "sc" but there is no "sc" left in the source
code.  This is a bit confusing, no?  So if we plan to make references to
lines of code, it make sense to have either the line numbering or the
labels (or both).  What do you think?

-- 
 Bastien

  reply	other threads:[~2009-07-17 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 10:44 [BUG] HTML exporting numbered literal examples Ulf Stegemann
2009-07-16 19:43 ` Bastien
2009-07-17 10:10   ` Ulf Stegemann
2009-07-17 14:50     ` Bastien [this message]
2009-07-17 21:08       ` Ulf Stegemann
2009-07-18  7:15         ` Bastien
2009-07-20 11:36           ` Ulf Stegemann
2009-07-23 19:58             ` Bastien
2009-07-24  6:38               ` Ulf Stegemann
2009-08-03  4:27 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y6qn9xed.fsf@bzg.ath.cx \
    --to=bastienguerry@googlemail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ulf-news@zeitform.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.