unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
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
Date: Tue, 18 May 2021 11:47:04 +0300	[thread overview]
Message-ID: <YKN/CM77ihqPBOXS@protected.localdomain> (raw)
In-Reply-To: <trinity-151deda7-141c-49b0-b925-bc8433817f10-1621290661505@3c-app-mailcom-bs06>

* michael-franzese@gmx.com <michael-franzese@gmx.com> [2021-05-18 01:32]:
>    Would like to delete and insert a string "s" only if there is no text
>    folloming point.
> 
>    (delete-region (point) (line-end-position))
>    (save-excursion (insert s))

(defun my-insert-on-eol (s)
  (when (eolp)
    (insert s)))


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/




      parent reply	other threads:[~2021-05-18  8:47 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
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 [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=YKN/CM77ihqPBOXS@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael-franzese@gmx.com \
    --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).