unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Psionic K <psionik@positron.solutions>
To: Psionic K <psionik@positron.solutions>
Cc: Eduardo Ochs <eduardoochs@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Dslide kmacro transcription & playback [was:Add moc to Non-GNU ELPA]
Date: Wed, 18 Dec 2024 00:28:14 +0900	[thread overview]
Message-ID: <CADQMGASA61tbzGCF6FoHS9tPYJ-3ercUVyU4yVxttWjqaZvQnw@mail.gmail.com> (raw)
In-Reply-To: <CADQMGAQT8EgWwaPLotz3=qzvo8zLFbBEC4OmmDCNPw_WAiJeOg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

Hello Eduard,

I force pushed some fixes onto the unstable branch.  The kmacro
transcription is pleasantly working and an action duplication bug was
identified and fixed.  I am nearly comfortable pushing to master and
tagging 0.6.0.

Here's the kmacro action commit
https://github.com/positron-solutions/dslide/commit/1123a4ecbe93d75816faa3ba9539d6aef4ed7ca3

For anyone interested, I've been keeping the `dslide-action' class stable
to keep custom actions stable.   However, I need a capability to choose the
next action correctly or to allow them to peek ahead and tell me which one
should be next.  Peeking may add complexity to actions but tracking their
progress for them adds rigidity.  If I decide to change actions, I'll make
sure they are absurdly simple to write after the changes.  I can always
leave an optional method to support more complex ordering.  Progress
tracking and reading options off of elements is the bulk of all action
creation, so doing it for them will make them brain dead simple.  I think
that's what we want.

The feature roadmap for 1.0 is here:
https://github.com/positron-solutions/dslide/issues/20

[-- Attachment #2: Type: text/html, Size: 1435 bytes --]

  reply	other threads:[~2024-12-17 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 16:52 Add moc to Non-GNU ELPA Psionic K
2024-12-17  4:40 ` Richard Stallman
2024-12-17  5:02   ` Psionic K
2024-12-17 12:00     ` Eduardo Ochs
2024-12-17 14:09       ` Psionic K
2024-12-17 15:28         ` Psionic K [this message]
2024-12-17 17:47         ` Eduardo Ochs
2024-12-18  1:01           ` Psionic K

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=CADQMGASA61tbzGCF6FoHS9tPYJ-3ercUVyU4yVxttWjqaZvQnw@mail.gmail.com \
    --to=psionik@positron.solutions \
    --cc=eduardoochs@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).