~zge

Old account, my new one is ~pkal

~zge/public-inbox

Last active a month ago
View more

Recent activity

Re: [PATCH] insert-kaomoji: Use true name of `load-file-name'. a month ago

From Philip Kaludercic to ~zge/public-inbox

Visuwesh Muthukumar <visuweshmuthukumar@gmail.com> writes:

> Hello,
>
> When using straight.el to install the package, which stores the
> elisp file as a symlink in the load path, this package fails to
> build `insert-kaomoji-alist'.  Using the true path of `load-file-name'
> fixes this issue.

Out of curiosity, if you wrap the entire expression in a
eval-when-compile block, does that change anything?

> Regards.
>

Re: [shell-command+] Push tag for release 2.2.0 2 months ago

From Philip Kaludercic to ~zge/public-inbox

Xinglu Chen <public@yoctocell.xyz> writes:

> On Tue, May 25 2021, Philip Kaludercic wrote:
>
>> Xinglu Chen <public@yoctocell.xyz> writes:
>>
>>> Hi,
>>>
>>> I am packaging your shell-command+ library for GNU Guix, version 2.2.0
>>> was just released, and it would be nice if you could push a new tag for
>>> it so I could point the source to the tag instead of having to specify
>>> the Git commit revision.
>>
>> Will do, the only issue is that there is a MELPA package (bang) that is

Re: [PATCH] Check for configuration in /etc/soju/config 2 months ago

From Philip Kaludercic to ~emersion/soju-dev

Simon Ser <contact@emersion.fr> writes:

> On Tuesday, May 25th, 2021 at 4:04 PM, Philip Kaludercic <philipk@posteo.net> wrote:
>
>> Simon Ser contact@emersion.fr writes:
>>
>> > Sorry, I've decided against this approach, and instead let the service
>> > specify `-config /etc/soju/config`.
>>
>> Hmm, ok. The reason I proposed this was because the Makefile made it
>> seems as though /etc/soju/config was checked by default, and I was
>> surprised to see that it was not the case, despite the docs saying
>>
>> -config <path>

Re: [PATCH] Check for configuration in /etc/soju/config 2 months ago

From Philip Kaludercic to ~emersion/soju-dev

Simon Ser <contact@emersion.fr> writes:

> Sorry, I've decided against this approach, and instead let the service
> specify `-config /etc/soju/config`.

Hmm, ok. The reason I proposed this was because the Makefile made it
seems as though /etc/soju/config was checked by default, and I was
surprised to see that it was not the case, despite the docs saying

    *-config* <path>
            Path to the config file. If unset, a default config file is used.

-- 
	Philip K.

[PATCH] Check for configuration in /etc/soju/config 2 months ago

From Philip Kaludercic to ~emersion/soju-dev

If no configuration path was specified, check if /etc/soju/config
exists before using the default configuration.
---
 cmd/soju/main.go    | 16 +++++++++++-----
 cmd/sojuctl/main.go | 16 +++++++++++-----
 2 files changed, 22 insertions(+), 10 deletions(-)

diff --git a/cmd/soju/main.go b/cmd/soju/main.go
index f7f8a42..5f94e2e 100644
--- a/cmd/soju/main.go
+++ b/cmd/soju/main.go
@@ -46,14 +46,20 @@ func main() {
	flag.Parse()

[message trimmed]

Re: [PATCH soju v2] Makefile: mark soju and sojuctl as .PHONY 2 months ago

From Philip Kaludercic to ~emersion/soju-dev

Alexey Yerin <yyp@disroot.org> writes:

> Otherwise running `make` didn't do anything on a non-clean state. Go
> deals with changed files automatically, and there's no real need to
> explicitly specify them.

I am not sure if this is the right fix, because now `go build` run every
time is invoked. 

This is an issue, if you want to build soju as a regular user, but
install it as root. The current Makefile re-builds soju as root
(downloading all the dependencies once again), which is not the expected
behaviour.

Re: [shell-command+] Push tag for release 2.2.0 2 months ago

From Philip Kaludercic to ~zge/public-inbox

Xinglu Chen <public@yoctocell.xyz> writes:

> OK, sounds good to me.  I will keep an eye on the repo :)

Don't worry about that, I will ping you when everything is done.

-- 
	Philip K.

Re: [shell-command+] Push tag for release 2.2.0 2 months ago

From Philip Kaludercic to ~zge/public-inbox

Xinglu Chen <public@yoctocell.xyz> writes:

> Hi,
>
> I am packaging your shell-command+ library for GNU Guix, version 2.2.0
> was just released, and it would be nice if you could push a new tag for
> it so I could point the source to the tag instead of having to specify
> the Git commit revision.

Will do, the only issue is that there is a MELPA package (bang) that is
currently depending on the same repository, so to avoid confusion, I
have requested it to be removed, before tagging a new version[0]. As
soon as that is done, I will push a new tag.

Re: Spurious 403 Responses 2 months ago

From Philip Kaludercic to ~emersion/soju-dev

Simon Ser <contact@emersion.fr> writes:

> On Monday, May 24th, 2021 at 12:39 PM, Simon Ser <contact@emersion.fr> wrote:
>
>> Can you submit this patch via git-send-email so that I can review
>> and merge it?
>
> If you aren't familiar with git-send-email: https://git-send-email.io/

Don't worry, I have used git-send-email before, I'm just used to
attaching patches to messages because most projects I contribute to
accept that too.

> If you prefer to submit the patch directly from sr.ht's web UI (like

[PATCH] Directly return messages to user 2 months ago

From Philip Kaludercic to ~emersion/soju-dev

From: Philip K <philipk@posteo.net>

---
 downstream.go | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/downstream.go b/downstream.go
index a4f2da8..3f8cf5a 100644
--- a/downstream.go
+++ b/downstream.go
@@ -1673,6 +1673,11 @@ func (dc *downstreamConn) handleMessageRegistered(msg *irc.Message) error {
		tags := copyClientTags(msg.Tags)

		for _, name := range strings.Split(targetsStr, ",") {
[message trimmed]