all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: 75004@debbugs.gnu.org
Subject: bug#75004: 30.0.92; documentation unclear about D-Bus support
Date: Sat, 21 Dec 2024 17:24:59 +0100	[thread overview]
Message-ID: <87v7vdngv8.fsf@gmx.de> (raw)
In-Reply-To: <87zfkpngys.fsf@gmx.de> (Michael Albinus's message of "Sat, 21 Dec 2024 17:22:51 +0100")

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

And here's the patch.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1773 bytes --]

diff --git a/doc/misc/dbus.texi b/doc/misc/dbus.texi
index 4d46564944f..1020e027774 100644
--- a/doc/misc/dbus.texi
+++ b/doc/misc/dbus.texi
@@ -75,9 +75,12 @@ Overview
 @cindex overview

 D-Bus is an inter-process communication mechanism for applications
-residing on the same host.  The communication is based on
-@dfn{messages}.  Data in the messages is carried in a structured way,
-it is not just a byte stream.
+residing on the same host.  Emacs uses it when it is compiled with the
+respective library, see configuration option @option{--with-dbus}.  At
+runtime, the form @code{(featurep 'dbusbind)} indicates D-Bus support.
+
+D-Bus communication is based on @dfn{messages}.  Data in the messages is
+carried in a structured way, it is not just a byte stream.

 The communication is connection oriented to two kinds of message
 buses: a so called @dfn{system bus}, and a @dfn{session bus}.  On a
diff --git a/doc/misc/tramp.texi b/doc/misc/tramp.texi
index 94e06ce6af3..b98b9b1fe5c 100644
--- a/doc/misc/tramp.texi
+++ b/doc/misc/tramp.texi
@@ -1365,9 +1365,12 @@ GVFS-based methods
 @acronym{GVFS} are mounted locally through @acronym{FUSE} and
 @value{tramp} uses this locally mounted directory internally.

-Emacs uses the D-Bus mechanism to communicate with @acronym{GVFS}@.
-Emacs must have the message bus system, D-Bus integration active,
-@pxref{Top, , D-Bus, dbus}.
+Emacs uses the D-Bus mechanism to communicate with @acronym{GVFS}@.  It
+must have been compiled with D-Bus support, @pxref{Top, , D-Bus, dbus}.
+
+@vindex tramp-gvfs-enabled
+The @code{tramp-gvfs-enabled} variable, being non-@code{nil}, signals
+that @value{tramp} can use @acronym{GVFS}-based methods.

 @table @asis
 @cindex method @option{afp}

  reply	other threads:[~2024-12-21 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21  1:08 bug#75004: 30.0.92; documentation unclear about D-Bus support Mike Kupfer
2024-12-21 16:22 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 16:24   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-21 22:53   ` Mike Kupfer

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=87v7vdngv8.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=75004@debbugs.gnu.org \
    --cc=kupfer@rawbw.com \
    --cc=michael.albinus@gmx.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.