emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: George Mauer <gmauer@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Utility of description lists
Date: Fri, 17 Jun 2022 08:41:53 -0500	[thread overview]
Message-ID: <CA+pajWJwiXj1re2O1g6Fm75LDBUOHzrXfLHFAJWZcWEatawP7w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2206170931340.8576@shell3.miskatonic.org>

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

It is not quite true that it's just a way of formatting, there is a
semantic element to it as well where someone parsing your document
programmatically can now know that what you have is a list of terms paired
with their descriptions. In fact, when exporting to html you get a
description list
<https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dl> which is one
of the most underused-yet-everyone-should-use-it-more html elements.

On Fri, Jun 17, 2022 at 8:37 AM William Denton <wtd@pobox.com> wrote:

> On 17 June 2022, Cletip Cletip wrote:
>
> > Final question : why do you use description lists and not another ?
>
> When I have a list of things I want to briefly descibe!  That's all.  It's
> just
> a way of formatting a list of things where there's a term (a word, a name,
> a
> title) that has some descriptive text.  Sometimes I use them when there's
> an
> obvious term/description pairing, and sometimes when I have a text-heavy
> list of
> things and I want to have a brief summary of each to make it easier to
> read.
>
>
> Bill
>
> --
> William Denton
> https://www.miskatonic.org/
> Librarian, artist and licensed private investigator.
> Toronto, Canada
>
>

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

  reply	other threads:[~2022-06-17 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 12:47 Utility of description lists Cletip Cletip
2022-06-17 13:35 ` William Denton
2022-06-17 13:41   ` George Mauer [this message]
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=CA+pajWJwiXj1re2O1g6Fm75LDBUOHzrXfLHFAJWZcWEatawP7w@mail.gmail.com \
    --to=gmauer@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).