Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Unable to use gnus on a nox build
Date: Fri, 29 Oct 2010 08:26:08 +0200	[thread overview]
Message-ID: <87k4l1jz0f.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3mxpynsv4.fsf@jhcloos.com> (James Cloos's message of "Thu, 28 Oct 2010 13:12:39 -0400")

On Thu, Oct 28 2010, James Cloos wrote:

> Adding a (setq tool-bar-mode nil) to .emacs worked.
>
> But that should not be required on a -nox emacs build.  It is just silly
> that everyone who wants to use gnus on a gui-less build should have to
> add that sexp to their .emacs.

The code checks if `tool-bar-mode' is bound and non-nil:

|   (when (and (not (featurep 'xemacs))
| 	       (boundp 'tool-bar-mode)
| 	       tool-bar-mode
| 	       ;; The Gnus 5.10.6 code checked (default-value 'tool-bar-mode).
| 	       ;; Why?  --rsteib
| 	       (or (not gnus-group-tool-bar-map) force))

If `tool-bar-mode' is non-nil in a no-X session, there is something
wrong, I'd say.  At least in Emacs 22.1, I have:

,----[ emacs -nw -Q -f ielm ]
| ELISP> tool-bar-mode
| nil
| ELISP> emacs-version
| "22.1.1"
`----

If this has changed in Emacs 24, I'd suggest to report it as a bug
(reproduce the failure and do M-x report-emacs-bug RET).

> And you cannot use the customize interface to do it; customize-variable
> does not see it because it is not marked to be customizable unless the
> emacs build supports a GUI mode.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2010-10-29  6:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  8:29 James Cloos
2010-10-27  7:01 ` Reiner Steib
2010-10-28 17:12   ` James Cloos
2010-10-29  6:26     ` Reiner Steib [this message]
2010-10-29  9:59     ` Julien Danjou
2010-10-29 19:10       ` Reiner Steib
2010-10-29 19:20         ` James Cloos

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=87k4l1jz0f.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.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).