emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bill White <billw@wolfram.com>
To: emacs-orgmode@gnu.org
Cc: devnull@Karl-Voit.at
Subject: Re: speed keys for plain lists?
Date: Thu, 12 May 2016 12:12:21 -0500	[thread overview]
Message-ID: <ruovb2jp5e2.fsf@wolfram.com> (raw)
In-Reply-To: 2016-05-10T10-20-32@devnull.Karl-Voit.at

On Tue May 10 2016 at 03:21, Karl Voit <devnull@Karl-Voit.at> wrote:

> * Bill White <billw@wolfram.com> wrote:
>>
>> Thank you all for the suggestions thus far.  I'll attach the org file
>> I'm working with:
>
> Being curious on your motivation: why do you use only plain list items
> instead of headings with paragraphs or headings with plain lists?

Mainly because I'm still playing around with possible formats.  Some
manual correction of the ocr text is required for each entry, which
provides a frictionless opportunity to add a little bit of list markup
and then get on with the next entry.

My final goal is a simple electronic version of the old Oxford English
Dictionary as outlined by Corey Doctorow
http://www.theguardian.com/technology/2013/aug/23/oxford-english-dictionary-future-digitally
based on files at the Internet Archive - volume 1 is at
https://archive.org/details/oed01arch

I'd like the thing to be as close to plaintext as possible with a
minimum of markup:
 - org list notation is minimal
 - it's useful within orgmode
 - it doesn't get in the user's way in non-emacs ecosystems
 - it avoids the endless quagmire of adding significant markup to such a
   huge body of text
 - it's a necessary first step for some other brave soul who wants to
   add markup & organization

But I'm open to suggestions & discussion - now's the time to play around
with formats to find the right balance between playing with words and
slogging through markup.  Perhaps this isn't the right mailing list for
that discussion, though.

Cheers -

bw
Bill White . billw@wolfram.com
"No ma'am, we're musicians."

  reply	other threads:[~2016-05-16 17:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 11:30 speed keys for plain lists? Bill White
2016-05-09 14:15 ` Bill White
2016-05-09 14:57   ` Kaushal Modi
2016-05-09 15:43     ` Marcin Borkowski
2016-05-09 16:58       ` John Kitchin
2016-05-09 17:27       ` Kaushal Modi
     [not found]       ` <153f4aedb6cc4ab181e9a168513c4a49@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-09 18:44         ` Eric S Fraga
2016-05-09 19:59           ` Bill White
2016-05-10  8:21             ` Karl Voit
2016-05-12 17:12               ` Bill White [this message]
2016-05-16 18:17                 ` Grant Rettke
2016-05-17 11:46                   ` Karl Voit
2016-05-17 15:54                   ` Bill White
2016-05-18  7:30                     ` Karl Voit
2016-05-19  2:48                     ` Grant Rettke
     [not found] ` <ccf2f9fe1b2e4df7a1dd48a046c6a86a@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-09 15:19   ` Eric S Fraga

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=ruovb2jp5e2.fsf@wolfram.com \
    --to=billw@wolfram.com \
    --cc=devnull@Karl-Voit.at \
    --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).