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: Sun, 22 Dec 2024 09:42:23 +0100	[thread overview]
Message-ID: <87o714nm6o.fsf@gmx.de> (raw)
In-Reply-To: <42621.1734821605@alto.camomileplus.org> (Mike Kupfer's message of "Sat, 21 Dec 2024 14:53:25 -0800")

Mike Kupfer <kupfer@rawbw.com> writes:

Hi Mike,

>> Could you pls check, whether the appended patch (for dbus.texi and
>> tramp.texi) helps?
>
> It does.  Thanks for the fast turnaround.

Thanks for the feedback. Pushed to the emacs-30 branch.

> BTW, I was surprised that 'configure' did not error out when I supplied
> --with-dbus (or --with-dbus=yes) on the command line.  I expect
> 'configure' to disable a feature (and exit with status 0) if the feature
> can't be provided and wasn't explicitly requested, but I thought the
> inability to provide a specifically requested feature was considered an
> error.  Am I misunderstanding how 'configure' is supposed to work?

I'm not an expert in this department. Eli?

> mike

Best regards, Michael.





  reply	other threads:[~2024-12-22  8:42 UTC|newest]

Thread overview: 6+ 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
2024-12-21 22:53   ` Mike Kupfer
2024-12-22  8:42     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-22 12:18       ` Eli Zaretskii

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=87o714nm6o.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.