unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: david larsson <david.larsson@selfhosted.xyz>
To: bokr@bokr.com
Cc: "Andrew Tropin" <andrew@trop.in>,
	"Ludovic Courtès" <ludo@gnu.org>,
	Tissevert <tissevert+guix@marvid.fr>,
	guix-devel@gnu.org,
	Guix-devel
	<guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org>
Subject: Re: Guix home and operating-system
Date: Thu, 28 Jul 2022 11:26:59 +0200	[thread overview]
Message-ID: <80e7fc6f3d7e89ad06077b59c6e6ff63@selfhosted.xyz> (raw)
In-Reply-To: <20220728002750.GA2606@LionPure>

> I use this to browse a bug by number:
> --8<---------------cut here---------------start------------->8---
> #!/usr/bin/bash
> # browse-bug
> 
> num="$(echo "$1"|tr -cs '0123456789' ' '|tr -d ' ')"
> 
> my_browser="${MY_BUG_BROWSER:-lynx}"
> if [ -n "$num" ];then
>     $my_browser "https://debbugs.gnu.org/cgi/bugreport.cgi?bug=$num"
> else
>     echo "\
> Usage: [MY_BUG_BROWSER=<your preference>] browse-bug BUG_NUMBER (not
> '$1' -> '$num')
>     BUG_NUMBER will be taken from \$1 word stripped of non-digits if 
> any
>     If you set MY_BUG_BROWSER to firefox-esr, you can run this in the
> background like
>         browse-bug '#56669' &
>     but lynx will want interaction from you on stdin, so no '&'
>     NB: if you Ctl-V the #, delete it or quote it, or bash will throw
> it away as comment.
> "
>     exit 1
> fi
> --8<---------------cut here---------------end--------------->8---

Useful idea, thanks!


      reply	other threads:[~2022-07-28  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06  9:20 Guix home and operating-system Tissevert
2022-07-08  8:12 ` Andrew Tropin
2022-07-18  9:38   ` Ludovic Courtès
2022-07-27  8:34     ` Andrew Tropin
2022-07-28  0:27       ` bokr
2022-07-28  9:26         ` david larsson [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=80e7fc6f3d7e89ad06077b59c6e6ff63@selfhosted.xyz \
    --to=david.larsson@selfhosted.xyz \
    --cc=andrew@trop.in \
    --cc=bokr@bokr.com \
    --cc=guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=tissevert+guix@marvid.fr \
    /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).