From: Akib Azmain Turja <akib@disroot.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Incorrectly indented form in Elisp manual
Date: Sat, 15 Oct 2022 20:11:00 +0600 [thread overview]
Message-ID: <877d116utn.fsf@disroot.org> (raw)
In-Reply-To: <83fsfp7cnx.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Oct 2022 10:45:38 +0300")
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Akib Azmain Turja <akib@disroot.org>
>> Date: Sat, 15 Oct 2022 12:14:17 +0600
>>
>> In Info, 24.6.2 Search-based Fontification:
>>
>> --8<---------------cut here---------------start------------->8---
>> (ANCHORED-MATCHER PRE-FORM POST-FORM
>> SUBEXP-HIGHLIGHTERS...)
>> --8<---------------cut here---------------end--------------->8---
>>
>> This is the result of this:
>>
>> --8<---------------cut here---------------start------------->8---
>> (@var{anchored-matcher} @var{pre-form} @var{post-form}
>> @var{subexp-highlighters}@dots{})
>> --8<---------------cut here---------------end--------------->8---
>>
>> Which should be this to format the output correctly on Info (and
>> probably on the book too):
>>
>> --8<---------------cut here---------------start------------->8---
>> (@var{anchored-matcher} @var{pre-form} @var{post-form}
>> @var{subexp-highlighters}@dots{})
>> --8<---------------cut here---------------end--------------->8---
>
> Thanks. I find no reason for wrapping this between two lines, so I
> just made it a single line.
Great! That will be easier to read.
--
Akib Azmain Turja
Find me on Mastodon at @akib@hostux.social, and on Codeberg (user
"akib").
This message is signed by me with my GnuPG key. Its fingerprint is:
7001 8CE5 819F 17A3 BBA6 66AF E74F 0EFA 922A E7F5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2022-10-15 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 6:14 Incorrectly indented form in Elisp manual Akib Azmain Turja
2022-10-15 7:45 ` Eli Zaretskii
2022-10-15 14:11 ` Akib Azmain Turja [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d116utn.fsf@disroot.org \
--to=akib@disroot.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.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).