Github messages for mblaze
 help / color / mirror / Atom feed
From: JNRowe <>
Subject: Re: [PR PATCH] [Updated] mcom: allow tilde prefixed path for profile's outbox setting
Date: Thu, 08 Oct 2020 13:42:25 +0200	[thread overview]
Message-ID: <20201008114225.1h49cEWagHHkIHaZYUHNE2BmdcFUch5s-AZDHPTBruo@z> (raw)
In-Reply-To: <>

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

There is an updated pull request by JNRowe against master on the mblaze repository master

mcom: allow tilde prefixed path for profile's outbox setting
I assumed – perhaps incorrectly – that my `outbox` setting could be `~/Mail/Sent`.  However, doing so fails because the tilde isn’t expanded.  This trivial change fixes that.



A patch file from is attached

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

From d114af08c9405eda32d28daf1e5185e8a41f2cb1 Mon Sep 17 00:00:00 2001
From: James Rowe <>
Date: Thu, 8 Oct 2020 11:25:45 +0100
Subject: [PATCH] mcom: allow tilde prefixed path for profile's outbox setting

 mcom | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mcom b/mcom
index a1a1f90..7bb3ce6 100755
--- a/mcom
+++ b/mcom
@@ -231,7 +231,7 @@ esac
 hdrs="$(printf '%s\n' "${hdrs#$NL}" | mhdr -)"
-outbox=$(mhdr -h outbox "$MBLAZE/profile")
+outbox=$(mhdr -h outbox "$MBLAZE/profile" | sed "s:^~/:$HOME/:")
 if [ -z "$outbox" ]; then
 	if [ -z "$resume" ]; then

  parent reply	other threads:[~2020-10-08 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 10:27 [PR PATCH] " JNRowe
2020-10-08 10:46 ` leahneukirchen
2020-10-08 11:42 ` JNRowe [this message]
2020-10-08 11:43 ` JNRowe
2020-10-08 12:27 ` [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201008114225.1h49cEWagHHkIHaZYUHNE2BmdcFUch5s-AZDHPTBruo@z \ \ \

* 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).