emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Cletip Cletip <clement020302@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Utility of description lists
Date: Fri, 17 Jun 2022 14:47:41 +0200	[thread overview]
Message-ID: <CAPHku6NN-31LdHR9t8aFqsPY5GJWL2gB0A+TDdJ8uv8-L-JhWg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

Hello to all,
The question is the same as the object, but it can be more detailed with
this question: what are the differences between description lists and other
lists?
After many researches, I can't understand the fundamental difference.
I can see two advantages to using this type of list:
- they are made implicitly to make a "key :: value" couple, which can be
convenient
- they can be useful when exporting: they have a different style than other
lists and can be used for some other things.

For example, with the use of org-roam (or even org-normal), if I want to
export a note with properties containing a link, I can't (the link is badly
exported). You can try with the following document :

:PROPERTIES:
:ID: 20220617115633324937
:SOURCE: [[id:20220617105453042719][Emacs]]
:CITE: [cite:@DifferenceSemantiqueEntre2022]
:END:
#+title: Test Page
#+OPTIONS: prop:t


- cite :: [cite:@DifferenceSemantiqueEntre2022]
- source :: [[id:20220617105453042719][Emacs]]

* Title and some content after here



Morehover, this type of data can be exploited by the Vulpea library (
https://github.com/d12frosted/vulpea), which could allow to add other
information to each note.

Final question : why do you use description lists and not another ?

PS : Thank you very much in advance for your future response, I discover
this original system to ask questions and I hope not to abuse it by asking
this type of questions ^^

[-- Attachment #2: Type: text/html, Size: 1608 bytes --]

             reply	other threads:[~2022-06-17 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 12:47 Cletip Cletip [this message]
2022-06-17 13:35 ` Utility of description lists William Denton
2022-06-17 13:41   ` George Mauer
2022-06-17 13:43   ` Fraga, Eric
2022-06-17 15:28     ` Cletip Cletip
2022-06-17 15:27   ` Cletip Cletip
2022-06-17 14:05 ` Kaushal Modi
2022-06-17 15:42   ` Cletip Cletip
2022-06-17 14:24 ` Juan Manuel Macías

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=CAPHku6NN-31LdHR9t8aFqsPY5GJWL2gB0A+TDdJ8uv8-L-JhWg@mail.gmail.com \
    --to=clement020302@gmail.com \
    --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).