Yuan Fu <yuf011@ucsd.edu> writes:

> The RSS feed seems to have duplicated sections. Take https://planet.emacslife.com/ for an example.

I believe the issue should be solved now, but I don't know if Planet
Emacslife will pick up on the change.

> Yuan

James Thomas <jimjoe@gmx.net> writes:

> Philip Kaludercic wrote:
>
>> I wouldn't concern myself too much with these kinds of things, if they
>> come at the cost of greater complexity.
>
> You're right.
>
>>> +(defun vc-backup-reset-make-backup-files (_ backend)
>>> +  "Reset the value of `vc-make-backup-files'. For use as advice to
>>> +`vc-switch-backend'."
>>> +  (if (eq backend 'Backup)
>>> +      (setq-local vc-make-backup-files t)

James Thomas <jimjoe@gmx.net> writes:

>>> +            (backup-file-name-p file))
>>> +    (unless vc-make-backup-files
>>> +      (setq-local vc-make-backup-files t))
>>
>> Why the `unless'?  There is no inherent harm in setting a buffer local
>> value to be the same as the global value.
>>
>
> I was thinking of perturbing the state as little as possible, while also
> saving a bit of memory. But that way would be fine too.

I wouldn't concern myself too much with these kinds of things, if they

James Thomas <jimjoe@gmx.net> writes:

> Normal backups are inhibited after vc-backup is enabled on a file due to
> the default setting of vc-make-backup-files. I use this patch to change
> this behaviour while keeping backups disabled for other backends.

Right, good point.

> diff --git a/vc-backup.el b/vc-backup.el
> index 5c6ca2e..097a035 100644
> --- a/vc-backup.el
> +++ b/vc-backup.el
> @@ -214,8 +214,11 @@ file."
>  ;;;###autoload

Daniel Mendler <mail@daniel-mendler.de> writes:

> On 9/12/23 12:02, Philip Kaludercic wrote:
>> Ihor Radchenko <yantar92@posteo.net> writes:
>> 
>>> Daniel Mendler <mail@daniel-mendler.de> writes:
>>>
>>>> ... Providing a public API won't work
>>>> since Compat is not included in Emacs itself. A design criterion of
>>>> Compat is also to keep the public API surface as small as possible.
>>>
>>> Maybe it is the time to consider including the compat.el API into Emacs?
>>> We are getting a number of :core packages published on ELPA and
>>> naturally having to solve various compatibility problems.

Ihor Radchenko <yantar92@posteo.net> writes:

> Daniel Mendler <mail@daniel-mendler.de> writes:
>
>> ... Providing a public API won't work
>> since Compat is not included in Emacs itself. A design criterion of
>> Compat is also to keep the public API surface as small as possible.
>
> Maybe it is the time to consider including the compat.el API into Emacs?
> We are getting a number of :core packages published on ELPA and
> naturally having to solve various compatibility problems.

I am a bit behind wrt Compat development.  Are we talking about adding
the `compat-call, etc. macros to the core?  So basically just a

john muhl <jm@pub.pink> writes:

> * lisp/progmodes/lua-ts-mode.el:
> * test/lisp/progmodes/lua-ts-mode-resources/indent.erts:
> * test/lisp/progmodes/lua-ts-mode-tests.el: New file.
> * etc/NEWS: Mention new mode.
> * lisp/progmodes/eglot.el (eglot-server-programs):
> * lisp/progmodes/hideshow.el (hs-special-modes-alist): Support
> lua-ts-mode.
> * admin/notes/tree-sitter/build-module/batch.sh:
> * admin/notes/tree-sitter/build-module/build.sh: Add Lua.
> * test/infra/Dockerfile.emba:
> * test/infra/test-jobs.yml: Include lua-ts-mode tests.
> ---

URL: https://github.com/karthink/popper

Yuan Fu <casouri@gmail.com> writes:

> Here’s the first draft for the tree-sitter progress report. sr.ht
> doesn’t seem to allow attachments? I had to paste the content in the
> email body.

I think I fixed this in the mailing list settings.

> Yuan

Looks good, I have added it to the draft for September:
https://amodernist.com/eaez/sep23.html#status:tree-sitter

>

Yuan Fu <casouri@gmail.com> writes:

> I wonder what format is preferred for submitting posts to the zine?
> Markdown or Org? Asking because I want to mark code with `` or ~~, and
> potentially code blocks too.

As the entire thing is just hand-written HTML[0], I am fine with
anything that I can easily (read using Pandoc) translate into HTML as
well.  So if you want to control how your text will look like in detail,
you can send me HTML and even add CSS if you want something, otherwise
what you insinuate seems to be Markdown, which is fine as well :)

[0] https://git.sr.ht/~pkal/elpa-zine/tree