From: Leo Prikler <leo.prikler@student.tugraz.at>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45272@debbugs.gnu.org, luis.felipe.la@protonmail.com
Subject: bug#45272: [PATCH] gnu: gnome-builder: Disable jedi plugin.
Date: Fri, 18 Dec 2020 18:10:02 +0100 [thread overview]
Message-ID: <b359cf2c40fe53579725faa5c70def979518de3e.camel@student.tugraz.at> (raw)
In-Reply-To: <87o8ir9hzk.fsf@gnu.org>
Am Freitag, den 18.12.2020, 17:49 +0100 schrieb Ludovic Courtès:
> Hi!
>
> Leo Prikler <leo.prikler@student.tugraz.at> skribis:
>
> > As pointed out in #45272, it is broken.
>
> Please add this as a comment above “-Dplugin_jedi=false” (refer to
> the
> bug by URL so there’s no ambiguity).
I feel like a side comment as in v2 would be wiser, so as to not
disrupt the sentence started before and to keep the sentiment, that it
should be enabled once someone has figured out, how to do so.
Of course, the side does not offer enough space for the full URL, so
that's bad. Would it suffice to add the URL to the commit message, so
one could `git blame` me?
Regards,
Leo
next prev parent reply other threads:[~2020-12-18 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 17:24 bug#45272: GNOME Builder: Global search, autocompletion, documentation don't work Luis Felipe via Bug reports for GNU Guix
2020-12-18 11:53 ` Leo Prikler
2020-12-18 14:16 ` bug#45272: [PATCH] gnu: gnome-builder: Disable jedi plugin Leo Prikler
2020-12-18 16:49 ` Ludovic Courtès
2020-12-18 17:10 ` Leo Prikler [this message]
2020-12-18 17:01 ` bug#45272: [PATCH v2] " Leo Prikler
2020-12-19 11:50 ` bug#45272: [PATCH v3] " Leo Prikler
2020-12-21 14:30 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b359cf2c40fe53579725faa5c70def979518de3e.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=45272@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=luis.felipe.la@protonmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).