From: uzibalqa <uzibalqa@proton.me>
To: Joel Reicher <joel.reicher@gmail.com>
Cc: Heime <heimeborgia@protonmail.com>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Get second character from comment-start
Date: Tue, 13 Aug 2024 13:36:46 +0000 [thread overview]
Message-ID: <J5UljGToHxgqEKO9yM730cDIyvCW78_MV_3DVqICH7C5dUsfKVbHLKyJ0pp8QIEn4Q-E9AEVPkMZ8K3SpSz4ifD3ZYkZNSxJ3elUUrIvm7A=@proton.me> (raw)
In-Reply-To: <86wmkkd7w7.fsf@gmail.com>
Sent with Proton Mail secure email.
On Tuesday, August 13th, 2024 at 10:39 PM, Joel Reicher <joel.reicher@gmail.com> wrote:
> Heime heimeborgia@protonmail.com writes:
>
> > On Tuesday, August 13th, 2024 at 5:15 PM, Joel Reicher
> > joel.reicher@gmail.com wrote:
> >
> > > Any reason not to do (aref ... 1)? Not sure what you're worried
> > > about.
> >
> > What is the standard way of capturing characters from strings,
> > is it with aref ?
>
>
> I don't know what makes something "standard" for you. As covered
> in (info "(elisp) String Basics") a string is an array, and as
> covered in (info "(elisp) Array Functions"), aref can be used to
> fetch an element of an array.
>
> And as a random sample of some core code, aref is used 17 times in
> files.el from what I can see. - Joel
I shall use aref as already done
prev parent reply other threads:[~2024-08-13 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 19:47 Get second character from comment-start Heime
2024-08-13 5:15 ` Joel Reicher
2024-08-13 8:10 ` Heime
2024-08-13 10:39 ` Joel Reicher
2024-08-13 13:36 ` uzibalqa [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='J5UljGToHxgqEKO9yM730cDIyvCW78_MV_3DVqICH7C5dUsfKVbHLKyJ0pp8QIEn4Q-E9AEVPkMZ8K3SpSz4ifD3ZYkZNSxJ3elUUrIvm7A=@proton.me' \
--to=uzibalqa@proton.me \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=joel.reicher@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.
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).