Github messages for mblaze
 help / color / mirror / Atom feed
From: JNRowe <JNRowe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] contrib/_mblaze: silence mseq errors
Date: Sat, 10 Oct 2020 15:25:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-188@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 431 bytes --]

There is a new pull request by JNRowe against master on the mblaze repository

https://github.com/JNRowe/mblaze master
https://github.com/leahneukirchen/mblaze/pull/188

contrib/_mblaze: silence mseq errors
On the first run or if you manually delete your sequence file, `mseq` errors will break your prompt when you hit tab.

Thanks,

James

A patch file from https://github.com/leahneukirchen/mblaze/pull/188.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-188.patch --]
[-- Type: text/x-diff, Size: 741 bytes --]

From f5bb905761c79b2d9591fee070045c6c61e8ad6d Mon Sep 17 00:00:00 2001
From: James Rowe <jnrowe@gmail.com>
Date: Sat, 10 Oct 2020 14:19:12 +0100
Subject: [PATCH] contrib/_mblaze: silence mseq errors

On the first run or if you manually delete your sequence file, mseq
errors will break your prompt when you hit tab.
---
 contrib/_mblaze | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/_mblaze b/contrib/_mblaze
index f58cb65..5255629 100644
--- a/contrib/_mblaze
+++ b/contrib/_mblaze
@@ -14,7 +14,7 @@ _mblaze_message() {
     _files "$expl[@]" && ret=0
   fi
 
-  curmsg=$(mseq .)
+  curmsg=$(mseq . 2>/dev/null)
   if [[ -z $curmsg || ! -f $curmsg ]]; then
     _message 'no current sequence'
     return $ret

             reply	other threads:[~2020-10-10 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10 13:25 JNRowe [this message]
2020-10-10 18:48 ` [PR PATCH] [Closed]: " leahneukirchen

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=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-188@inbox.vuxu.org \
    --to=jnrowe@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).