~pkal

Erlangen, Bavaria

https://amodernist.com/

CS student. Find me also on Libera, using pkal as my nick.


I use: git | todo | lists

~pkal/public-inbox

Last active a day ago

~pkal/compat-devel

Last active 3 months ago

~pkal/elpa-zine

Last active 3 months ago

~pkal/compat-announce

Last active 3 months ago
View more

Recent activity

Re: site-lisp and sub directory handling a day ago

From Philip Kaludercic to ~pkal/public-inbox

TAKAHASHI Yoshio <yfb02119@nifty.com> writes:

> Philip-san,
>
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> I
>> have now pushed a commit to the repository (e2dca35d) that should
>> implement the feature -- but haven't tested it yet, so please say if
>> you
>> notice any issues.
>
> Unfortunately, it does not work as expected.
>

Re: site-lisp and sub directory handling 6 days ago

From Philip Kaludercic to ~pkal/public-inbox

TAKAHASHI Yoshio <yfb02119@nifty.com> writes:

> Philip-san,
>
> Philip Kaludercic <philipk@posteo.net> writes:
>
>>>> While possible, I don't get what advantage to doing this.
>>> It generates .auto-site.el in subdirectory, I can use/call functions in
>>> subdirectores el-files without load those el-files explicitly.
>> I get that, that is the point of autoloads, what I wanted to know is if
>> you had a use-case for separating autoload files for each directory,
>> instead of gathering them all in the "root" directory.
>
> I worry we have mis-communication.

Re: site-lisp and sub directory handling 9 days ago

From Philip Kaludercic to ~pkal/public-inbox

TAKAHASHI Yoshio <yfb02119@nifty.com> writes:

> Philip-san,
>
> Philip Kaludercic <philipk@posteo.net> writes:
>
>>> But, my expectation is to generate autoload-file(s) from
>>> site-lisp/**/*.el when I set `site-lisp-directory' to site-lisp/.
>> No, that is not what the package offers.  All it currently does is to
>> load ./*.el and ./**/&.el in `site-lisp-directory',
>
>>> and does not have
>>> autoloads of site-lisp/*/*.el.  Is this expected?
>> No, those files _should_ also be loaded.

Re: site-lisp and sub directory handling 13 days ago

From Philip Kaludercic to ~pkal/public-inbox

TAKAHASHI Yoshio <yfb02119@nifty.com> writes:

> Philip-san,
>
> Thank you for your reply, I try to explain cases in my side, my
> expectation, and experience.
>
> Philip Kaludercic <philipk@posteo.net> writes:
>
>>> In my case, I have:
>>>   ~/.emacs.d/site-lisp
>>>   ~/.emacs.d/site-lisp/progmodes
>
>> That sounds like a reasonable feature,  but I wouldn't want to hard-code

Re: site-lisp and sub directory handling 15 days ago

From Philip Kaludercic to ~pkal/public-inbox

TAKAHASHI Yoshio <yfb02119@nifty.com> writes:

> Philip-san,

Hi,

> I have a question about site-lisp sub directory handling.
>
> In my case, I have:
>   ~/.emacs.d/site-lisp
>   ~/.emacs.d/site-lisp/progmodes
> and set `site-lisp-directory' to "site-lisp" (default).
> In this case, `site-lisp-prepare' tries to traverse "progmodes"
> directory, but fails to add its autoloads.

Re: [PATCH] site-lisp: Bump copyright year to 2024 19 days ago

From Philip Kaludercic to ~pkal/public-inbox

Jeremy Bryant <jb@jeremybryant.net> writes:

> From 089ec9b53abcee31ac0d31976e1bc2cd817e01af Mon Sep 17 00:00:00 2001
> From: Jeremy Bryant <jb@jeremybryant.net>
> Date: Wed, 7 Feb 2024 23:25:00 +0000
> Subject: [PATCH] * site-lisp.el:  Bump copyright year to 2024
>
> ---
>  site-lisp.el | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/site-lisp.el b/site-lisp.el
> index 1092cbc..784063b 100644
> --- a/site-lisp.el

Re: Use setopt in :option on Emacs 29.1+ a month ago

From Philip Kaludercic to ~pkal/public-inbox

Joseph Turner <joseph@breatheoutbreathe.in> writes:

> Hi Philip!

Hi,

> Does this make sense?

I would say no, because there would be no point to using :option?  I
consider the macro a mistake anyway, since it has no
context-sensitivity.  The only reason I can think of would be if you are
expecting to use the configuration on different systems with different
version...

Re: [QUESTION] setup.el: Why does :global use global-set-key and not define-key? 2 months ago

From Philip Kaludercic to ~pkal/public-inbox

Niall Dooley <dooleyn@gmail.com> writes:

> On Wed, 20 Dec 2023 at 19:03, Philip Kaludercic <philipk@posteo.net> wrote:
>> Just looking at the definition of global-set-key, it should be more or
>> less like:
>>
>>   (define-key (current-global-map) key command)
>>
>> >              so would it not be better to use the more primitive
>> > function within a macro definition?
>>
>> I don't know of any such rule when writing macros.
>
> I didn't mean to suggest their was such a rule.

Re: [QUESTION] setup.el: Why does :global use global-set-key and not define-key? 2 months ago

From Philip Kaludercic to ~pkal/public-inbox

Niall Dooley <dooleyn@gmail.com> writes:

> Hi Philip,

Hi,

> Why does setup-define :global use
>
> `(global-set-key ,key ,command)
>
> and not something like
>
> `(define-key global-map ,key ,command)?
>

Re: Can you please change the package name for setup.el 2 months ago

From Philip Kaludercic to ~pkal/public-inbox

Niall Dooley <dooleyn@gmail.com> writes:

> How about setpkg so it is similar to the new setopt?

I believe there was a similar suggestion wrt. to including "pkg" or
"package" in the name, which I still do not really like, because of the
implication that the setup macro is directly related to packages.