From: fatiparty--- via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Playing down the text in org-mode
Date: Thu, 13 Jan 2022 21:53:54 +0100 (CET) [thread overview]
Message-ID: <MtKCyNv--3-2@tutanota.com> (raw)
In-Reply-To: <87iluncrr6.fsf@posteo.net-MtK5wx2----2>
Jan 14, 2022, 08:20 by maciaschain@posteo.net:
> fatiparty@tutanota.com writes:
>
>> I am discussing something slightly different.
>>
>> Here is normal text within -which there is some understated text- before continuing with normal text.
>>
>
> Yes, it seems that I have understood you horribly wrong, sorry for the
> noise (it must be the effects of the third modern vaccine that they gave
> me yesterday :-)
>
> In short, what you want is that a part of the text is "obscured" in some
> way with respect to the main body text, and you would like Org to have
> some marks for it. I see an important basic problem: there are many
> procedures to reduce the reading importance of a text: simply pass that
> text to a footnote, use dashes, parentheses or brackets, put the text in
> a smaller size (which is the usual when these passages are isolated
> paragraphs). I think it is better to define all these questions in the
> output formats, through post-processing, and in Org use macros, custom
> links, special blocks, the procedure that John has shared here, etc.
>
> But a "universal" no-emphasis mark doesn't seem viable to me, IMHO.
>
Are there any universal marks to charge the typeface used. That can be more
general. If I do something in emacs-lisp I would still need some form of
containment characters.
> Best regards,
>
> Juan Manuel
>
next prev parent reply other threads:[~2022-01-13 20:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 18:27 Playing down the text in org-mode fatiparty--- via General discussions about Org-mode.
2022-01-13 18:50 ` Juan Manuel Macías
2022-01-13 19:04 ` John Kitchin
2022-01-13 19:19 ` Juan Manuel Macías
2022-01-13 19:31 ` fatiparty--- via General discussions about Org-mode.
[not found] ` <87bl0feahc.fsf@posteo.net-MtJnHBm----2>
2022-01-13 19:15 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 19:22 ` John Kitchin
2022-01-13 19:42 ` Juan Manuel Macías
2022-01-13 19:53 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 20:20 ` Juan Manuel Macías
2022-01-13 20:51 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 1:50 ` Ihor Radchenko
[not found] ` <87iluncrr6.fsf@posteo.net-MtK5wx2----2>
2022-01-13 20:53 ` fatiparty--- via General discussions about Org-mode. [this message]
2022-01-13 21:39 ` Juan Manuel Macías
2022-01-14 9:41 ` Eric S Fraga
[not found] ` <874k66irh4.fsf@ucl.ac.uk-MtMyJM6----2>
2022-01-14 13:03 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 13:30 ` Eric S Fraga
[not found] ` <87o84efnqk.fsf@ucl.ac.uk-MtNobqT----2>
2022-01-14 13:44 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 14:13 ` Eric S Fraga
2022-01-14 19:27 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 20:00 ` Juan Manuel Macías
2022-01-14 20:25 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 20:41 ` Juan Manuel Macías
2022-01-14 20:45 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 20:57 ` Juan Manuel Macías
[not found] ` <87zgnydp8d.fsf@posteo.net-MtPKW6j----2>
2022-01-14 21:00 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 21:16 ` Juan Manuel Macías
[not found] ` <87r19adnm9.fsf@posteo.net-MtPRzO3----2>
2022-01-14 22:01 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 22:23 ` Juan Manuel Macías
2022-01-14 22:31 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 22:44 ` Juan Manuel Macías
2022-01-14 21:40 ` Tim Cross
[not found] ` <878rvjco35.fsf@posteo.net-MtKOBaG----2>
2022-01-13 22:45 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 23:08 ` Juan Manuel Macías
2022-01-14 0:18 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 19:58 ` fatiparty--- via General discussions about Org-mode.
[not found] ` <CAJ51ETrfC31Pt8HdWdqFSOsmeQ+vZLx1Vv14=tjyHCBQuumZuw@mail.gmail.com-MtJu4nE----2>
2022-01-13 19:42 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 21:27 ` Tim Cross
2022-01-13 22:27 ` fatiparty--- via General discussions about Org-mode.
2022-01-13 22:35 ` fatiparty--- via General discussions about Org-mode.
2022-01-14 1:55 ` Ihor Radchenko
[not found] ` <87ee5b5bet.fsf@localhost-MtLHUmb----2>
2022-01-14 2:04 ` fatiparty--- via General discussions about Org-mode.
-- strict thread matches above, loose matches on Subject: below --
2022-01-14 19:26 autofrettage
2022-01-16 12:00 ` 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=MtKCyNv--3-2@tutanota.com \
--to=emacs-orgmode@gnu.org \
--cc=fatiparty@tutanota.com \
--cc=maciaschain@posteo.net \
/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).