unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: 29473@debbugs.gnu.org
Subject: bug#29473: 25.3; 'background-mode is 'light on console with black background
Date: Sat, 02 Dec 2017 10:25:47 -0500	[thread overview]
Message-ID: <87a7z1jgn8.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87efoj3h91.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Mon, 27 Nov 2017 14:53:30 +0000")

Tim Landscheidt <tim@tim-landscheidt.de> writes:

> In newsticker tree view on a Linux console with black back-
> ground (both KDE's konsole application and "native" console
> (Alt-Ctrl-F2), all under Fedora),

> (frame-parameter nil 'background-mode) returns 'light.  This
> also happens with Emacs' current master branch.
>
> After glancing at the manual, I'm unclear whether:
>
> 1. Emacs should set 'background-mode correctly by itself
>    (and thus there is an error in the detection mechanism),
>
> 2. it is my duty to explicitly set background-mode (via
>    initial-frame-alist?) when using Emacs on a console, or

I'm pretty sure it's #1, the manual explains that background-mode nil
should use automatic detection, and it sounds like that detection is
going wrong.

I don't see anything in lisp/term/linux.el that sets the background mode
at all.  What does running 'echo $TERM' in a shell give you?

Looking at lisp/term/konsole.el, it looks like it uses the xterm
functions for everything.  Could you try stepping through/adding
'message' calls in terminal-init-xterm and see if/where it goes wrong?






  reply	other threads:[~2017-12-02 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 14:53 bug#29473: 25.3; 'background-mode is 'light on console with black background Tim Landscheidt
2017-12-02 15:25 ` Noam Postavsky [this message]
2017-12-09  5:35   ` Tim Landscheidt
2017-12-09 14:05     ` Noam Postavsky
2021-09-03  6:44       ` Lars Ingebrigtsen
2021-10-03  9:44         ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87a7z1jgn8.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=29473@debbugs.gnu.org \
    --cc=tim@tim-landscheidt.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 public inbox

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

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