piem-use-magit: Unconditionally set to t

When piem is loaded, piem-use-magit is enabled if Magit has already
been loaded.  This approach is potentially confusing: a user may want
to use Magit, be happy that it seems to just work, and then confused
when it doesn't work in some later session where loading Magit happens
to not be triggered before loading piem.

All the relevant sites have fboundp guards (and those are cheap), so
there's no advantage to disabling this if Magit isn't enabled at load
time.  Set piem-use-magit to t by default.

Message-Id: <20210522203905.16504-3-kyle@kyleam.com>

2 files changed, 5 insertions, 6 deletions

diff --git a/Documentation/piem.texi b/Documentation/piem.texi
index 0f5235c..ca6a97b 100644
--- a/Documentation/piem.texi
+++ b/Documentation/piem.texi
@@ -265,11 +265,10 @@ for a particular call.
 
 @cindex magit
 @vindex piem-use-magit
-When piem loads, it detects whether Magit is loaded and sets
-@code{piem-use-magit} accordingly.  If that option is non-nil, piem uses
-Magit for some operations, particularly those that are user-facing.
-This includes jumping to the Magit status buffer for a code repository
-after applying a patch.
+If that option is non-nil and Magit is loaded, piem uses Magit for some
+operations, particularly those that are user-facing.  This includes
+jumping to the Magit status buffer for a code repository after applying
+a patch.
 
 @findex piem-am-ready-mbox
 Note that the @code{piem-am} command works only for buffers from which
diff --git a/piem.el b/piem.el
index 780df00..c273138 100644
--- a/piem.el
+++ b/piem.el
@@ -139,7 +139,7 @@ the return value of `piem-mid'."
   "Which git executable to use."
   :type 'string)
 
-(defcustom piem-use-magit (featurep 'magit)
+(defcustom piem-use-magit t
   "Whether to use Magit for some user-facing operations."
   :type 'boolean)