unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: michael-franzese@gmx.com
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Skip Montanaro <skip.montanaro@gmail.com>,
	Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Determining existence of text following point
Date: Tue, 18 May 2021 10:24:20 +0200	[thread overview]
Message-ID: <trinity-9010972a-3bc2-4ea8-b7e3-a18b03a269f3-1621326260578@3c-app-mailcom-bs13> (raw)
In-Reply-To: <87zgwsx5r3.fsf@ericabrahamsen.net>

Would like to set a function which I could then use with an if statement

Have constructed something as follows.  But naturally the name of the function is
the reverse of having no text (including empty spaces)

(defun looking-at-text ()
  "todo"

    (looking-at-p "\\([[:blank:]]+\\)?\\(\n\\|\\'\\)")

    )

Then my condition for inserting my string would be

(unless (looking-at-text)
   (delete-region (point) (line-end-position))
   (save-excursion (insert s)) )



> Sent: Tuesday, May 18, 2021 at 12:09 PM
> From: "Eric Abrahamsen" <eric@ericabrahamsen.net>
> To: michael-franzese@gmx.com
> Cc: "Skip Montanaro" <skip.montanaro@gmail.com>, "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Determining existence of text following point
>
> michael-franzese@gmx.com writes:
>
> > But if there are only empty spaces it is ok too.
>
> Ah, then Skip's looking-at is a fine solution:
>
> (looking-at-p "\\([[:blank:]]+\\)?\\(\n\\|\\'\\)")
>
> That's as a test. Or you could use a single `replace-regexp' invocation,
> to detect and replace the whitespace in one go.
>



  parent reply	other threads:[~2021-05-18  8:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 21:46 Determining existence of text following point michael-franzese
2021-05-17 22:02 ` Skip Montanaro
2021-05-17 22:31   ` michael-franzese
2021-05-17 23:05     ` Eric Abrahamsen
2021-05-17 23:15       ` michael-franzese
2021-05-17 23:36         ` Skip Montanaro
2021-05-18  0:09         ` Eric Abrahamsen
2021-05-18  0:37           ` michael-franzese
2021-05-18  8:24           ` michael-franzese [this message]
2021-05-18  8:56           ` Jean Louis
2021-05-18  9:31             ` Christopher Dimech
2021-05-18  9:42               ` Jean Louis
2021-05-18  9:54               ` Jean Louis
2021-05-18 10:08                 ` Christopher Dimech
2021-05-18 11:07                   ` tomas
2021-05-18 11:26                     ` Christopher Dimech
2021-05-18 11:56                       ` Jean Louis
2021-05-18 12:23                         ` Christopher Dimech
2021-05-18 12:35                           ` tomas
2021-05-18 12:50                             ` Christopher Dimech
2021-05-18 12:02                       ` tomas
2021-05-18 12:15                         ` Christopher Dimech
2021-05-18 12:27                           ` tomas
2021-05-18 12:43                             ` Christopher Dimech
2021-05-18 12:44                             ` Jean Louis
2021-05-18 12:28                         ` Christopher Dimech
2021-05-18 12:47                           ` Jean Louis
2021-05-18 20:50             ` michael-franzese
2021-05-18 22:04               ` Jean Louis
2021-05-18 22:17               ` Jean Louis
2021-05-19  7:28                 ` michael-franzese
2021-05-19  8:05                   ` michael-franzese
2021-05-19 10:23                   ` Jean Louis
2021-05-19 10:32                     ` michael-franzese
2021-05-19 12:31                     ` michael-franzese
2021-05-17 23:53       ` michael-franzese
2021-05-18  8:47     ` 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=trinity-9010972a-3bc2-4ea8-b7e3-a18b03a269f3-1621326260578@3c-app-mailcom-bs13 \
    --to=michael-franzese@gmx.com \
    --cc=eric@ericabrahamsen.net \
    --cc=help-gnu-emacs@gnu.org \
    --cc=skip.montanaro@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).