discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 1/2] piem-use-magit: Reword docstring to clarify scope
Date: Sat, 22 May 2021 16:39:04 -0400	[thread overview]
Message-ID: <20210522203905.16504-2-kyle@kyleam.com> (raw)
In-Reply-To: <20210522203905.16504-1-kyle@kyleam.com>

This option isn't really about using Magit wherever possible, but, as
the manual already states, using Magit for some user-facing
 piem.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/piem.el b/piem.el
index 78536f1..780df00 100644
--- a/piem.el
+++ b/piem.el
@@ -140,7 +140,7 @@ (defcustom piem-git-executable
   :type 'string)
 (defcustom piem-use-magit (featurep 'magit)
-  "Whether to use Magit where possible."
+  "Whether to use Magit for some user-facing operations."
   :type 'boolean)
 (defcustom piem-default-branch-function

  reply	other threads:[~2021-05-22 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 20:39 [PATCH 0/2] piem-use-magit tweaks Kyle Meyer
2021-05-22 20:39 ` Kyle Meyer [this message]
2021-05-22 20:39 ` [PATCH 2/2] piem-use-magit: Unconditionally set to t Kyle Meyer

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:

  List information: https://git.kyleam.com/

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

  git send-email \
    --in-reply-to=20210522203905.16504-2-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --subject='Re: [PATCH 1/2] piem-use-magit: Reword docstring to clarify scope' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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