From: Drew Adams <drew.adams@oracle.com>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : mark multi regions, kill and yank
Date: Wed, 1 Nov 2023 15:00:11 +0000 [thread overview]
Message-ID: <SJ0PR10MB54881854408B5B24CA81F88BF3A7A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87r0larm1p.fsf@mat.ucm.es>
> I downloaded the hightlight.el file, again, from wiki, and the
> function we talked about it, is still not in. So I wait.
As I said, you can just use the old names,
`hlt-(un)highlight-regions' instead of
`hlt-(un)highlight-zones.el'. And you have
`zz-add-zones-from-highlighting' as well.
I don't expect to finish the changes I started
in highlight.el soon. So don't bother to wait.
> Just a suggestion, but wouldn't it be easier, if you would push zones
> and hightlight to some repo, which is publicly available.
Not for me, no. Anyone is welcome to mirror
the files from Emacs Wiki to a GIT repo (and
that should already be happening, with the
Emacsmirror repo).
If it's too hard to download two files from
Emacs Wiki, add their directory to your
`load-path', and `require' them, then perhaps
look for another way to do what you want.
I have only the one suggestion; if it doesn't
work for you then try something else.
> > If you want to be sure to have the latest versions
> > of any of my files then download them from the wiki.
>
> As I said the functions we were talking about are not in wiki.
I've already explained about what's available
on the wiki: the latest externalized versions.
If they help you do what you want, great. If
not, then perhaps someone else will be able
to help you more.
prev parent reply other threads:[~2023-11-01 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 16:02 mark multi regions, kill and yank Uwe Brauer
2023-10-30 17:11 ` Bob Newell
2023-10-30 17:56 ` Uwe Brauer
2023-10-30 19:56 ` Bob Newell
2023-10-30 17:32 ` [External] : " Drew Adams
2023-10-30 17:54 ` Uwe Brauer
2023-10-30 19:39 ` Drew Adams
2023-10-30 20:32 ` Uwe Brauer
2023-10-30 21:42 ` Drew Adams
2023-10-31 8:53 ` Uwe Brauer
2023-10-31 16:39 ` Drew Adams
2023-10-31 16:52 ` Uwe Brauer
2023-10-31 17:48 ` Drew Adams
2023-10-31 20:36 ` Uwe Brauer
2023-10-31 21:08 ` Drew Adams
2023-11-01 7:05 ` Uwe Brauer
2023-11-01 15:00 ` Drew Adams [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=SJ0PR10MB54881854408B5B24CA81F88BF3A7A@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=oub@mat.ucm.es \
/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).