all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oliver Laslett <oliver@cytora.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Rami Ylimäki" <rami.ylimaki@vincit.fi>, 30917@debbugs.gnu.org
Subject: bug#30917: 26.0.91; True color emacs in termite
Date: Fri, 23 Mar 2018 19:51:01 +0000	[thread overview]
Message-ID: <DEFE8CE5-691A-4245-BEC4-F00AA9212C26@cytora.com> (raw)
In-Reply-To: <83woy2haud.fsf@gnu.org>

Rami, Eli,

I’ve realised that calling ‘sudo’ is just resulting in emacs with no theme and colours are inherited from my terminal theme (.Xresources). But the problem still remains that emacs is not detecting that termite is true colour. I have checked that terminfo defines setfg and setbg. 

Thanks



On 23 Mar 2018, at 19:04, Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Oliver Laslett <oliver@cytora.com>
>> Date: Fri, 23 Mar 2018 10:30:47 +0000
>> 
>> I have some odd behviour in emacs 26.0.91 with my color theme.
>> I am using termite terminal emulator (with true color support) and
>> when running `emacs -nw` I get a broken theme using reduced color set.
>> However, if I run `sudo emacs -nw` my theme shows correctly.
>> 
>> As I understand, emacs determines true color support using terminfo. Is
>> emacs calling a command that may require root user privileges? How could
>> I debug this (apologies, long term emacs user, first bug report!)?
> 
> Rami, could you please look into this?
> 
> Thanks.





  reply	other threads:[~2018-03-23 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 10:30 bug#30917: 26.0.91; True color emacs in termite Oliver Laslett
2018-03-23 19:04 ` Eli Zaretskii
2018-03-23 19:51   ` Oliver Laslett [this message]
2018-03-24  0:19     ` Rami Ylimäki
2018-03-26 10:12       ` Oliver Laslett
2018-03-26 15:14         ` Eli Zaretskii
2018-03-27 22:21           ` Rami Ylimäki

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=DEFE8CE5-691A-4245-BEC4-F00AA9212C26@cytora.com \
    --to=oliver@cytora.com \
    --cc=30917@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rami.ylimaki@vincit.fi \
    /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.