From: rakoo <rakoo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mcom: Document how attachments work
Date: Wed, 24 Apr 2024 19:07:45 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-259@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
There is a new pull request by rakoo against master on the mblaze repository
https://github.com/rakoo/mblaze doc-attachments
https://github.com/leahneukirchen/mblaze/pull/259
mcom: Document how attachments work
Reopening of https://github.com/leahneukirchen/mblaze/pull/234 with a proper branch that doesn't change as I fiddle with it
A patch file from https://github.com/leahneukirchen/mblaze/pull/259.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-doc-attachments-259.patch --]
[-- Type: text/x-diff, Size: 862 bytes --]
From ca6162a2c310b6eed648bd850de5da0552612c5b Mon Sep 17 00:00:00 2001
From: Matthieu Rakotojaona <m@rako.space>
Date: Mon, 27 Feb 2023 15:33:13 +0100
Subject: [PATCH] mcom: Document how attachments work
---
man/mcom.1 | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/man/mcom.1 b/man/mcom.1
index 957c322..08592c7 100644
--- a/man/mcom.1
+++ b/man/mcom.1
@@ -130,6 +130,13 @@ Delete the draft and quit.
Preview the draft, using
.Xr mshow 1 .
.El
+.Sh ATTACHMENTS
+From within the editor, attachments are added by setting an Attach: header with the path to the desired files. Multiple Attach: headers can be added.
+
+To add from the commandline, use
+.Sq mcom Fl attach No path/to/file
+and the header will be added automatically.
+It is possible to use tilde (~) in the file path.
.Sh ENVIRONMENT
.Bl -tag -width Ds
.It Ev EDITOR , Ev VISUAL
next reply other threads:[~2024-04-24 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 17:07 rakoo [this message]
2024-06-06 11:13 ` [PR PATCH] [Updated] " rakoo
2024-06-06 11:25 ` rakoo
2024-09-08 9:45 ` thimc
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-259@inbox.vuxu.org \
--to=rakoo@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).