From: Philip Kaludercic <philipk@posteo.net>
To: tomas@tuxteam.de
Cc: carlmarcos@tutanota.com, help-gnu-emacs@gnu.org
Subject: Re: Tools for those working heavily with strings
Date: Sun, 24 Jul 2022 13:20:47 +0000 [thread overview]
Message-ID: <87fsiqhck0.fsf@posteo.net> (raw)
In-Reply-To: <Yt1GfBOinlGz84si@tuxteam.de> (tomas@tuxteam.de's message of "Sun, 24 Jul 2022 15:17:48 +0200")
tomas@tuxteam.de writes:
> On Sun, Jul 24, 2022 at 01:42:14PM +0200, carlmarcos@tutanota.com wrote:
>> Jul 24, 2022, 11:26 by tomas@tuxteam.de:
>>
>> > On Sun, Jul 24, 2022 at 01:12:39PM +0200, carlmarcos--- via Users
>> > list for the GNU Emacs text editor wrote:
>> >
>> > [...]
>> >
>> >> I'd appreciate if emacs could provide a minimum set of functions
>> >> to manipulate list,
>> >> as string manipulations are of good use.
>> >>
>> >
>> > Why do you always refuse to read the docs?
>> >
>> >> What can be introduced, you think?
>> >>
>> >
>> > What is missing, from your point of view?
>> >
>> What can I use to test whether a string in composed of whitespace or is empty?
>
> Try (string-match-p "^[[:space:]]*$" your-string-here)
Or `string-empty-p'.
> If you want it to only match "horizontal white space" (i.e. no newlines,
> no vertical tabs), try :blank: instead.
>
> Cheers
next prev parent reply other threads:[~2022-07-24 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 5:04 Tools for those working heavily with strings carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-24 5:11 ` Jean Louis
2022-07-24 5:17 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-24 8:45 ` Jean Louis
2022-07-24 8:44 ` Jean Louis
2022-07-24 11:12 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-24 11:26 ` tomas
2022-07-24 11:42 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-24 13:11 ` Arash Esbati
2022-07-24 13:17 ` tomas
2022-07-24 13:20 ` Philip Kaludercic [this message]
2022-07-24 13:23 ` tomas
2022-07-24 14:45 ` Philip Kaludercic
2022-07-24 20:04 ` Jean Louis
2022-07-24 20:00 ` Jean Louis
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=87fsiqhck0.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=carlmarcos@tutanota.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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).