[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] speed keys for plain lists?
From: |
Karl Voit |
Subject: |
Re: [O] speed keys for plain lists? |
Date: |
Wed, 18 May 2016 09:30:33 +0200 |
User-agent: |
slrn/pre1.0.0-18 (Linux) |
* Bill White <address@hidden> wrote:
>
> Here's a sample of my second iteration. A poor man's database - still
> pure orgmode and still plain text, but easily parsable:
>
> - main word|subordinate word, subdivided into grammatical relations A, B, C,
> &c.
> - identification
> - main form :: Abbacy
> - obsolete † :: no
> - non-naturalized ‖ :: no
> - pronunciation :: æ•băsi
> - part of speech :: substantive
> - specification :: none
> - status :: default
> - spellings :: 5-6 abbasy, 6-7 abbacie
> - inflections :: none
> - [morphology]
> - derivation (etymology) :: A modification of the earlier
> ABBATIE, assimilated to forms like prelacy, mediaeval Latin
> -acia, -atia.
> - subsequent form-history ::
> - miscellaneous facts ::
> - TODO: significations & illustrative quotations
I am certainly not thinking of all of your use-cases. However, here
is a possible alternative «solution» with headings. Just being
curious: What disadvantages do you see here compared to lists?
*** main word|subordinate word, subdivided into grammatical relations A, B, C,
&c.
:PROPERTIES: ## or: :identification:-drawer
:mainform: Abbacy
:obsolete: no
:nonnaturalized: no
:pronunciation: æ•basi
:partofspeech: substantive
:specification: none
:status: default
:spellings: 5-6 abbasy, 6-7 abbacie
:...OR...:
:spelling: 5-6 abbasy
:spelling: 6-7 abbacie
:inflections: none
:END:
#+COMMENT: Previous list as properties does have multiple advantages
#+COMMENT: such as column view (+ corresponding edit functionality)
#+COMMENT: Following lines seem to contain potential multi-line
#+COMMENT: text which does not qualify to be handled well in properties:
- [morphology]
- derivation (etymology) :: A modification of the earlier
ABBATIE, assimilated to forms like prelacy, mediaeval Latin
-acia, -atia.
- subsequent form-history ::
- miscellaneous facts ::
**** TODO: significations & illustrative quotations
#+COMMENT: I personally prefer todos that can possible get SCHEDULED
#+COMMENT: and/or DEADLINE dates to be headings.
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
- Re: [O] speed keys for plain lists?, (continued)
- Re: [O] speed keys for plain lists?, Marcin Borkowski, 2016/05/09
- Re: [O] speed keys for plain lists?, John Kitchin, 2016/05/09
- Re: [O] speed keys for plain lists?, Kaushal Modi, 2016/05/09
- Message not available
- Re: [O] speed keys for plain lists?, Eric S Fraga, 2016/05/09
- Re: [O] speed keys for plain lists?, Bill White, 2016/05/09
- Re: [O] speed keys for plain lists?, Karl Voit, 2016/05/10
- Re: [O] speed keys for plain lists?, Bill White, 2016/05/16
- Re: [O] speed keys for plain lists?, Grant Rettke, 2016/05/16
- Re: [O] speed keys for plain lists?, Karl Voit, 2016/05/17
- Re: [O] speed keys for plain lists?, Bill White, 2016/05/17
- Re: [O] speed keys for plain lists?,
Karl Voit <=
- Re: [O] speed keys for plain lists?, Grant Rettke, 2016/05/18
Message not available