From: "Clément Lassieur" <clement@lassieur.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 35606-done@debbugs.gnu.org,
"Clément Lassieur" <clement@lassieur.org>,
"Raghav Gururajan" <rvgn@disroot.org>
Subject: bug#35606: Gajim
Date: Tue, 14 May 2019 15:48:14 +0200 [thread overview]
Message-ID: <CAMj_LPMoWZGtA0d-FdT-Lx1KiogwAUkVdWHzaEueG5PUkNEckg@mail.gmail.com> (raw)
In-Reply-To: <878sv98caq.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Thank you Ricardo for fixing and Raghav for reporting this bug I introduced!
Sorry not to have more time to work on it at the moment.
Clément
On Tue, May 14, 2019, 2:13 PM Ricardo Wurmus <rekado@elephly.net> wrote:
>
> Raghav Gururajan <rvgn@disroot.org> writes:
>
> >> I fixed this with commit a624c3631077aa3fa5c05849579932c5b67b985c. When
> >> GAJIM_PLUGIN_PATH is not set it will not be added to the list of
> >> directories that are searched for plugins.
> >
> > Thank you very much Ricardo! Just to be clear, the path get
> > automatically added with this fix right?
>
> No. I only made it so that when GAJIM_PLUGIN_PATH is not set it won’t
> be added to the list of directories that Gajim looks at, so there’s no
> crash. If GAJIM_PLUGIN_PATH *is* set the directory it points at will be
> added to the list.
>
> --
> Ricardo
>
>
[-- Attachment #2: Type: text/html, Size: 1362 bytes --]
next prev parent reply other threads:[~2019-05-14 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 19:21 bug#35606: Gajim Raghav Gururajan
2019-05-06 19:40 ` Tobias Geerinckx-Rice
2019-05-07 19:27 ` Ricardo Wurmus
2019-05-07 19:47 ` Ricardo Wurmus
2019-05-13 7:04 ` Ricardo Wurmus
2019-05-13 7:08 ` Raghav Gururajan
2019-05-14 12:12 ` Ricardo Wurmus
2019-05-14 13:48 ` Clément Lassieur [this message]
2019-05-14 13:56 ` Raghav Gururajan
2019-05-06 19:45 ` Raghav Gururajan
2019-05-06 19:49 ` Raghav Gururajan
2019-05-11 9:48 ` Raghav Gururajan
2019-05-11 10:02 ` Ricardo Wurmus
2019-05-11 10:11 ` Raghav Gururajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMj_LPMoWZGtA0d-FdT-Lx1KiogwAUkVdWHzaEueG5PUkNEckg@mail.gmail.com \
--to=clement@lassieur.org \
--cc=35606-done@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=rvgn@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.