emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Cletip Cletip <clement020302@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Utility of description lists
Date: Fri, 17 Jun 2022 17:42:58 +0200	[thread overview]
Message-ID: <CAPHku6OqdfNeZHTFd+WBi40pFsuYGn+H57gb=c9bZbsinLpVDQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY1_82VTDrDigC0a3N=LNonwwfCwr4vK20QyhKsts4B9Yg@mail.gmail.com>

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

Ok I understand, it's really nice (the rendering on your site too).
Thanks for your answer

Le ven. 17 juin 2022 à 16:05, Kaushal Modi <kaushal.modi@gmail.com> a
écrit :

> On Fri, Jun 17, 2022 at 8:50 AM Cletip Cletip <clement020302@gmail.com>
> wrote:
>
> > Final question : why do you use description lists and not another ?
>
> I use description lists *heavily*.
>
> 1. For description lists of course.. where the "description" part is a
> bit verbose and plain lists don't look at that elegant
>
> For example, this in Org
>
> =====
> ****** Customizing ~local.mk~ (Optional)
> Here are few variables that you might like to change in the ~local.mk~:
> - ~prefix~ :: Org installation directory
>   #+begin_src makefile
>   prefix = /dir/where/you/want/to/install/org # Default: /usr/share
>   #+end_src
>   The ~.el~ files will go to ~$(prefix)/emacs/site-lisp/org~ by
>   default. If you'd like to change that, change the ~lispdir~
>   variable too.
> - ~infodir~ :: Org Info installation directory. I like to keep the
>   Info file for development version of Org in a separate directory.
>   #+begin_src makefile
>   infodir = $(prefix)/org/info # Default: $(prefix)/info
>   #+end_src
> - ~ORG_MAKE_DOC~ :: Types of Org documentation you'd like to build by
>   default.  Setting below generates only the Org Info manual.
>   #+begin_src makefile
>   ORG_MAKE_DOC = info # Default: html pdf
>   #+end_src
> =====
>
> exports to
> https://scripter.co/building-org-development-version/#customizing-local-dot-mk--optional
>
> 2. Where something would belong in a sub-heading, but not quite
> exactly? I can only describe that using one of my examples:
>
> =====
> ***** Using ~pip install~
> If you do not want to manually download the ~.jar~, there's a Python
> wrapper available to do the same for you:
> [[https://github.com/svenkreiss/html5validator][html5validator]].
> - Install ::
>   #+begin_src shell
>   pip install --user html5validator
>   #+end_src
> - Run ::
>   #+begin_src shell
>   html5validator --root public/
>   #+end_src
>   It seems like this Python wrapper implicitly passes ~--skip-non-html
> =====
>
> exports to https://scripter.co/offline-html5-validator/#using-pip-install
>
> 3. Sometimes I also use it for adding Notes to a section
>
> =====
> - Note :: While the =%.1f= format is handy for those who are used to
>           =printf()= syntax, note that Calc unlimited precision
>           numbers are converted to double floats before applying
>           =%.1f=. Whereas =f1= operates on Calc numbers without
>           conversion.
> =====
>
> exports to the Note in
> https://scripter.co/field-formatters-in-org-table/#using-calc-f1-formatter
>

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

  reply	other threads:[~2022-06-17 15:44 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
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 [this message]
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='CAPHku6OqdfNeZHTFd+WBi40pFsuYGn+H57gb=c9bZbsinLpVDQ@mail.gmail.com' \
    --to=clement020302@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    /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).