emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: FR: source code
Date: Wed, 9 Jan 2008 22:21:47 +0000	[thread overview]
Message-ID: <20080109222147.GM18716@atlantic.linksys.moosehall> (raw)
In-Reply-To: <20080109175019.GC22499@odin.demosthenes.org>

On Wed, Jan 09, 2008 at 11:50:20AM -0600, Russell Adams wrote:
> > I definite agree with that.  I, too, primarily use org-mode for the  
> > way things
> > look in Emacs.  I occasionally export but my main use is within emacs.
> > 
> > Thanks,
> > Ed

Same here.  A legible and easy to type .org format is very important
for me.

> I guess I'm missing the point. Optional tags to improve syntax
> highlighting in code snippets or to improve export wouldn't affect how
> your buffers look inside Emacs. You aren't obligated to use them. ;]

It *is* possible to simultaneously achieve beautiful clean text with
non-obtrusive semantic markup, and keep good flexibility in export
format options; reStructuredText is living proof of this:

  http://docutils.sourceforge.net/docs/ref/rst/introduction.html

Compare the following documents:

  http://docutils.sourceforge.net/docs/user/rst/quickstart.html
  http://docutils.sourceforge.net/docs/user/rst/quickstart.txt

I would *love* to see orgmode reuse more of these great ideas.

> On the flip side as a frequent exporter, I welcome anything that can
> help unobtrusively improve the quality of the output. Adding syntax
> highlighting in export, or a simple way to escape code metacharacters
> would be of great benefit to me.
> 
> I've recently gotten completely hooked on the Latex exporter. The
> ability to turn an org outline from my project notes into a
> professional looking PDF with bookmarks is invaluable! All that with
> zero time spent formatting on my part.

Hear hear, agreed on all accounts!

  reply	other threads:[~2008-01-09 22:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 11:22 FR: source code Phil Jackson
2008-01-08 14:03 ` Bastien
     [not found]   ` <b71b18520801082003h7baccfa9t3a0cf936c07c086a@mail.gmail.com>
2008-01-09  4:04     ` Eddward DeVilla
2008-01-09 17:33       ` Ed Hirgelt
2008-01-09 17:50         ` Russell Adams
2008-01-09 22:21           ` Adam Spiers [this message]
2008-01-16  0:36         ` Bastien
2008-01-16  1:21           ` Eddward DeVilla
2008-01-16  1:55             ` Bastien
2008-01-16  2:33           ` Tim Stewart
2008-01-16 12:05             ` Bastien
2008-01-16 16:03               ` Tim Stewart
2008-01-16 16:21 ` Carsten Dominik
2008-01-16 18:59   ` Phil Jackson
2008-01-18  8:20     ` Carsten Dominik
2008-01-18  9:59       ` Phil Jackson
2008-01-29 16:04         ` Phil Jackson
2008-01-29 18:20           ` Rick Moynihan
2008-01-29 18:32             ` Russell Adams
2008-01-29 18:49               ` Phil Jackson
2008-01-30  7:02             ` Bastien Guerry
2008-01-30  7:17           ` Bastien Guerry
2008-02-05 16:51           ` 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=20080109222147.GM18716@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).