From: ram <chat@rj95.be>
To: "João Távora" <joaotavora@gmail.com>
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: question regarding my emacs package
Date: Tue, 13 Jun 2023 21:46:12 +0000 [thread overview]
Message-ID: <cXWmFOUS4ULEvGMkbJm51-KGt8cmRJOcnIiansE_xmLsAYk57TRsholTlgL7R6kKFHfsi_DW8qMFIVULxh-QsrYLQyCqtYArh9wyrG_gTpM=@rj95.be> (raw)
In-Reply-To: <CALDnm5069-aTLvJ4ZfCNtNSY+xVK5ZOs4tgWjbwd_KVDhf1J=A@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
terser is always welcomed. is there a cute analog for dropping breadcrumbs (ie tracking a buffer position in my package's parlance) for a trail?
------- Original Message -------
On Tuesday, June 13th, 2023 at 1:13 PM, João Távora <joaotavora@gmail.com> wrote:
>
>
> On Tue, Jun 13, 2023 at 1:36 AM ram chat@rj95.be wrote:
>
> > i agree. fwiw i’m not opposed to a name change if it comes to it
>
>
> If you accept my suggestion, it would be trail.el which pleasantly
> much shorter than breadcrumbs.el
>
> João
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
wnUEARYKACcFgmSI44sJkLWF/Pp8PQPNFiEExUjWugOWGzBgCQZvtYX8+nw9
A80AAM11AQDuFaHO7YAhVbX92wbOGT5iHWunRpSMGIEXVi2JL77zMwEAy7o8
fuyUHVZPnVMSHh6AnrwAjxKaFVhXXCs9NYxy4gI=
=FIIS
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2023-06-13 21:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 3:18 question regarding my emacs package ram
2023-06-07 15:53 ` Philip Kaludercic
2023-06-07 18:04 ` Philip Kaludercic
2023-06-07 19:45 ` ram
2023-06-07 19:48 ` Philip Kaludercic
2023-06-07 19:50 ` ram
2023-06-07 22:34 ` ram
2023-06-08 7:13 ` ram
2023-06-08 7:26 ` Philip Kaludercic
2023-06-08 18:50 ` ram
2023-09-08 7:40 ` Philip Kaludercic
2023-06-11 11:41 ` Madhu
2023-06-12 12:52 ` Madhu
2023-06-12 16:40 ` Andrea Corallo
2023-06-13 4:01 ` Madhu
2023-06-13 8:55 ` Andrea Corallo
2023-06-13 9:19 ` Madhu
2023-06-13 23:55 ` Michael Heerdegen
2023-06-14 16:10 ` Mattias Engdegård
2023-06-16 3:53 ` Michael Heerdegen
2023-06-16 4:46 ` Madhu
2023-06-16 15:28 ` Michael Heerdegen
2023-06-17 3:01 ` ram via Emacs development discussions.
2023-06-18 0:40 ` Michael Heerdegen
2023-06-29 19:28 ` ram
2023-06-11 18:49 ` João Távora
2023-06-11 19:08 ` ram via Emacs development discussions.
2023-06-12 8:45 ` Philip Kaludercic
2023-06-12 10:23 ` João Távora
2023-06-12 10:54 ` Philip Kaludercic
2023-06-12 20:43 ` João Távora
2023-06-13 0:36 ` ram via Emacs development discussions.
2023-06-13 18:13 ` João Távora
2023-06-13 21:46 ` ram [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='cXWmFOUS4ULEvGMkbJm51-KGt8cmRJOcnIiansE_xmLsAYk57TRsholTlgL7R6kKFHfsi_DW8qMFIVULxh-QsrYLQyCqtYArh9wyrG_gTpM=@rj95.be' \
--to=chat@rj95.be \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=philipk@posteo.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).