Skip to content

(WIP) Complete tempo compatibility#191

Closed
DevelopmentCool2449 wants to merge 1 commit intominad:mainfrom
DevelopmentCool2449:main
Closed

(WIP) Complete tempo compatibility#191
DevelopmentCool2449 wants to merge 1 commit intominad:mainfrom
DevelopmentCool2449:main

Conversation

@DevelopmentCool2449
Copy link
Copy Markdown
Collaborator

@DevelopmentCool2449 DevelopmentCool2449 commented Jan 9, 2026

Part of #188 and emacs-devel thread discussions

tempel-define-template and tempel-interactive are almost complete here, I just need to add more tempo commands here.

For now, these are inside tempel.el instead of a separate file (tempel-tempo.el) since some modifications to the core code are needed.

I am showing this as a small preview of what I have done.

@minad
Copy link
Copy Markdown
Owner

minad commented Jan 9, 2026

Thanks! Sounds good. Maybe tempel-tempo.el could just be called tempo.el and provide aliases and shims under their original name? We should aim to make tempo.el as small as possible. Of course, features which are useful for Tempel itself like tempel-define-template could just live in tempel.el.

@minad
Copy link
Copy Markdown
Owner

minad commented Jan 11, 2026

For orientation I think it makes sense to check which packages inside Emacs require Tempo, and to ensure that the required functionality is available. I found snmp-mode, dcl-mode and probably most importantly org-tempo. Furthermore we could scan ELPA and MELPA or the emacsmirror.

@DevelopmentCool2449
Copy link
Copy Markdown
Collaborator Author

DevelopmentCool2449 commented Jan 11, 2026

Thanks! Sounds good. Maybe tempel-tempo.el could just be called tempo.el and provide aliases and shims under their original name? We should aim to make tempo.el as small as possible. Of course, features which are useful for Tempel itself like tempel-define-template could just live in tempel.el.

I think tempo.el will be moved to the lisp/obsolete directory once tempel has landed, so I think having a tempel-tempo.el file would be a better option, but for the moment, I'm focusing on having the essentials of tempo.el in tempel, and then see where all these changes would be stored.

For orientation I think it makes sense to check which packages inside Emacs require Tempo, and to ensure that the required functionality is available. I found snmp-mode, dcl-mode and probably most importantly org-tempo. Furthermore we could scan ELPA and MELPA or the emacsmirror.

Yes, I'm looking for which tempo functions or variables are most used.

Edit: tempel-tempo-add-tag, tempel-tempo-define-template and tempel-tempo-use-tag-list are now (mostly) complete

@DevelopmentCool2449 DevelopmentCool2449 force-pushed the main branch 9 times, most recently from 63b95ea to d5aff68 Compare January 13, 2026 04:29
@DevelopmentCool2449
Copy link
Copy Markdown
Collaborator Author

DevelopmentCool2449 commented Jan 13, 2026

A small update: I've ported the tempo-test.el, and all of them run successfully.

However, there are some changes in Tempel code that I'm not sure if Tempel should support.

One is the (complete) support for the syntax (P ...), which, unlike the variant (p ..., forces to use the minibuffer for prompt.

And the support for tempo-insert-string-functions.

@DevelopmentCool2449 DevelopmentCool2449 force-pushed the main branch 2 times, most recently from 3fa150e to 7877a6f Compare January 13, 2026 18:37
Comment thread tempel.el
@minad
Copy link
Copy Markdown
Owner

minad commented Jan 13, 2026

I've invited you to this repository. If you want, you can work on a branch here. Besides that, feel free to make uncontroversial changes like this directly: 4ed454c. This way you can keep this PR more focused on the compatibility layer only.

Comment thread tempel-tempo.el
@DevelopmentCool2449
Copy link
Copy Markdown
Collaborator Author

I've invited you to this repository. If you want, you can work on a branch here. Besides that, feel free to make uncontroversial changes like this directly: 4ed454c. This way you can keep this PR more focused on the compatibility layer only.

Thanks, that sounds good, but only until I finish this.

@DevelopmentCool2449
Copy link
Copy Markdown
Collaborator Author

I created the tempel-compatibility branch. I'm closing this to continue the discussion in #192

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants