From: Jean Louis <bugs@gnu.support>
To: michael-franzese@gmx.com
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
Skip Montanaro <skip.montanaro@gmail.com>,
Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Determining existence of text following point
Date: Wed, 19 May 2021 01:17:01 +0300 [thread overview]
Message-ID: <YKQ83Re7WqgqHqBE@protected.localdomain> (raw)
In-Reply-To: <trinity-03505dfd-f49e-4a65-a258-6b6e6c82dd42-1621371051118@3c-app-mailcom-bs13>
* michael-franzese@gmx.com <michael-franzese@gmx.com> [2021-05-18 23:52]:
> For instance, if the text in a commented string as follows, I will go ahead with
> the insertion.
>
(defun my-insert-on-empty-end-of-line (s)
(let ((line-cut (buffer-substring-no-properties (point) (line-end-position))))
(when (or (not (string-match "[^[:blank:]]" line-cut)) (eolp))
(insert s))))
(defun my-insert-on-empty-end-of-line (s)
(let ((line-cut (buffer-substring-no-properties (point) (line-end-position))))
(when (or (not (string-match "[^+[:blank:];-]" line-cut)) (eolp))
(insert s))))
(defun my-insert ()
(interactive)
(my-insert-on-empty-end-of-line "Hello"))
(local-set-key (kbd "<f5>") 'my-insert)
Line with blanks, works:
;; Hello
Line with something else but our series of chars (does not work, expected):
;; █ abc
Line with fancy stuff that we wish to include (works):
;; ;;;;;;;;;;;;;;;;Hello;;;;;;;;;;;;;;;;;;;;;;
;; +++++++++++++++++++++Hello+++++++++++++
;; -------------------------Hello------Hello
Weird other lines (it does not work, as it is so expected):
;; 𝓒𝓾𝓻𝓼𝓸𝓻 𝓲𝓼 𝓱𝓮𝓻𝓮: █ 𝓫𝓾𝓽 𝓲𝓼 𝓷𝓸𝓽 𝔀𝓸𝓻𝓴𝓲𝓷𝓰, 𝐄𝐗𝐏𝐄𝐂𝐓𝐄𝐃!
--
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/
next prev parent reply other threads:[~2021-05-18 22:17 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 [this message]
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=YKQ83Re7WqgqHqBE@protected.localdomain \
--to=bugs@gnu.support \
--cc=eric@ericabrahamsen.net \
--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).