From: William Denton <wtd@pobox.com>
To: Vikas Rawal <vikasrawal@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Displaying macros differently
Date: Sun, 4 Dec 2022 22:43:41 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2212042239440.27314@shell3.miskatonic.org> (raw)
In-Reply-To: <CALtzAB3+93MQfgWZ+zKQg_xyjOCoNt37WTgHz_h41S0j5Whs1A@mail.gmail.com>
On 4 December 2022, Vikas Rawal wrote:
> I frequently use orgmode macros -- like {{{M(Year 1998--99)}}} -- in tables
> designed for latex export. I find that the macro syntax occupies many
> character spaces. At the very least, 9 spaces are taken up even if my macro
> shortcut is just one character long. This is very difficult with wide
> tables as often the tables go off the screen just because of this.
>
> I was wondering if there is a simple way of making org display the macros
> differently. That is, use some kind of overlay, and display the above macro
> may be like M:Year 1998--99. Or some special character could be used to
> denote that there is a macro underlying what is visible here.
Is this close enough?
(setq org-hide-macro-markers t)
That hides the {{{macro}}} curly brackets (if there's no leading space).
I also have this to toggle macro visibility in the document so I can see them
when I want to:
#+begin_src emacs-lisp
(defun wtd/toggle-org-macro-markers ()
"Toggle visibility of {{{macro}}} markers"
(interactive)
(setq org-hide-macro-markers (not org-hide-macro-markers))
(font-lock-mode)
(font-lock-mode))
#+end_src
I think there's been some discussion about evaluating the macros and showing the
result, but I don't think that's possible.
Bill
--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada
next prev parent reply other threads:[~2022-12-05 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 16:00 Displaying macros differently Vikas Rawal
2022-12-05 3:43 ` William Denton [this message]
2022-12-05 16:53 ` Vikas Rawal
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=alpine.DEB.2.22.394.2212042239440.27314@shell3.miskatonic.org \
--to=wtd@pobox.com \
--cc=emacs-orgmode@gnu.org \
--cc=vikasrawal@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).