On 10/05/23 20:45, Milan Glacier wrote:
>On 10/05/23 10:41, Bartosz Bubak wrote:
>>Dnia Wed, Oct 04, 2023 at 05:06:51PM -0400, Milan Glacier napisał(a):
>>
>>>If so, you can try to rebuild those autoloads files, here is the steps:
>>>
>>>1. Launching the emacs.
>>>2. Deleting everything from `my-loaddefs.el`.
>>>3. M-x my/update-all-autoloads.
>>>4. Restart emacs
>>
>>Hi,
>>Unfortunately it's not working, as I understand configs aren't fully loaded and emacs doesn't see the function `my/update-all-autoloads` [No match]
>>There's any other way to load/execute this function ?

On 10/05/23 10:41, Bartosz Bubak wrote:
>Dnia Wed, Oct 04, 2023 at 05:06:51PM -0400, Milan Glacier napisał(a):
>
>> If so, you can try to rebuild those autoloads files, here is the steps:
>>
>> 1. Launching the emacs.
>> 2. Deleting everything from `my-loaddefs.el`.
>> 3. M-x my/update-all-autoloads.
>> 4. Restart emacs
>
>Hi,
>Unfortunately it's not working, as I understand configs aren't fully loaded and emacs doesn't see the function `my/update-all-autoloads` [No match]
>There's any other way to load/execute this function ?
>

Bartosz Bubak <bartosz.bubak@gmail.com> writes:

> Hey,
> I have been using your emacs setup from=20
> https://git.sr.ht/~northyear/dotemacs for some time now, but a few=20
> days ago I
> encountered some strange issues.
> The first one was for Doom themes, none of them load and return an=20
> error:
>
> lambda-`-'-text-obj17: invalid argument type: keymapp, nil
>
> I tried to figure out what the problem was, but to no avail=20
> (unfortunately I'm bad at lisp and green at emacs), I just deleted

Protesilaos Stavrou <info@protesilaos.com> writes:

>>
>> Interestingly, I find that evaluating the following code:
>>
>>      (set-background-color "#000000")
>>
>> will let emacs uses the ansi "black" color
>> from your terminal's colorsheme (which is just the backround 
>> for
>> modus-vivendi). However, if I change the code to:
>>
>>      (set-background-color "#0F0000")

On 22/12/05 09:52AM, Protesilaos Stavrou wrote:
>> From: North Year <ny-ml@outlook.com> Date: Mon,  5 Dec 2022 02:27:08
>> -0500
>>
>> Protesilaos Stavrou <info@protesilaos.com> writes:
>>
>>> Emacs in a terminal cannot produce colours outside the range
>>> specified by those first 16 values.  So if your default “black” is
>>> something like “#1a1a1a” then ’modus-vivendi’ will default to that
>>> instead of what should be “#000000”.
>
>> This is indeed the reason!  Changing the colorscheme of my terminal
>> emulator solve the issue.
>

Protesilaos Stavrou <info@protesilaos.com> writes:

>
>     some-symbol-here)))

It's "yio" or "yao" to select a symbol. Vim and emacs's word are
different things. Vim uses "iskeyword" to configure what forms a 
word,
while emacs uses "modify-syntax-entry"

Hi Prot,

Hope you are doing well!

Recently I surprisingly find that you started to use evil. By 
looking at
your source code I am really sorry to hear that you injured your 
left
hand. I hope you could recover from it soon!

I highly recommends two packages (they are exclusive) in an effort 
to
avoid control keys as much as possible.

> Yes:
>
> https://man.sr.ht/builds.sr.ht/triggers.md

Got it!

Thank you!

Is it possible to send email notification to a destinated mail 
(mailist
or personal email) for failed builds?

As I am starting to use sourcehut, a all email and no web UI flow 
is all
I expect.

Protesilaos Stavrou <info@protesilaos.com> writes:

> Emacs in a terminal cannot produce colours outside the range specified
> by those first 16 values.  So if your default “black” is something like
> “#1a1a1a” then ’modus-vivendi’ will default to that instead of what
> should be “#000000”.

Thanks for your quick response! This is indeed the reason!
Changing the colorscheme of my terminal emulator solve the issue.

This is indeed something unexpecteed.
I never expect that emacs cannot generate colors outside the first 16 colors.
I was thought that an “xterm-256color” terminal with “$COLORTERM=truecolor” would be sufficient enough for accurate color dispaly.