unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson via Bug reports for GNU Guix <bug-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 58321@debbugs.gnu.org
Subject: bug#58321: make issues.guix.gnu.org a little easier in the desktop
Date: Thu, 06 Oct 2022 13:17:00 -0400	[thread overview]
Message-ID: <871qrk27oz.fsf@dismail.de> (raw)
In-Reply-To: <87fsg1uy1n.fsf@gmail.com> (zimoun's message of "Thu, 06 Oct 2022 11:00:20 +0200")

zimoun <zimon.toutoune@gmail.com> writes:

> Hi,
>
> On mer., 05 oct. 2022 at 21:20, jbranso--- via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
>
>> We could perhaps:
>>
>> 1 number each message and sidebar link
>>
>> 2 highlight which link in the sidebar that corresponds to the currently 
>> viewed message.
>
> I agree it could be helpful.  Just a minor workaround while waiting a
> fix. :-)
>
> For complex thread, what I do (when I do not use the Emacs front-end of
> Debbugs :-)) is to read them using a Web frontend of some public-inbox
> instance.  For instance,
>
>  1. I click to the icon download [1],
>  2. search Message-ID (here line 43),
>  3. copy/stash it (here 87fulrsqxx.fsf@gnu.org),
>  4. paste it to the navigation bar appending the public-inbox URL (here
>  https://yhetil.org/guix/).
>
> Last, I am usually interested by the thread overview so I add ’/#r’ to
> the URL, as in [2].
>
>
> 1: <https://issues.guix.gnu.org/issue/24937/raw/10>
> 2: <https://yhetil.org/guix/87fulrsqxx.fsf@gnu.org/#r>
>
>
> Cheers,
> simon
>

Thanks for sharing your workflow!




      reply	other threads:[~2022-10-06 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 21:04 bug#58321: make issues.guix.gnu.org a little easier in the desktop jbranso--- via Bug reports for GNU Guix
2022-10-05 21:20 ` jbranso--- via Bug reports for GNU Guix
2022-10-06  9:00   ` zimoun
2022-10-06 17:17     ` Joshua Branson via Bug reports for GNU Guix [this message]

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=871qrk27oz.fsf@dismail.de \
    --to=bug-guix@gnu.org \
    --cc=58321@debbugs.gnu.org \
    --cc=jbranso@dismail.de \
    --cc=zimon.toutoune@gmail.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).