unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Mario Castelán Castro" <marioxcc.MT@yandex.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs -nw niggles
Date: Tue, 29 Aug 2017 14:06:13 -0500	[thread overview]
Message-ID: <2d0e8771-567c-4b9f-8840-cedb3ed7d2e1@yandex.com> (raw)
In-Reply-To: <20170829171211.B57F5301033@cspc120.cs.man.ac.uk>

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

On 29/08/17 12:12, Richard Banach wrote:
> hi,
> 
> it's not quite like yours ... i attach two screenshots
> 
> 1) with proper menu bar ... this is emacs running in its own window
> with a color scheme it got from somewhere ... pale and cute but less
> helpful for me
> 
> 2) with pretend black menu bar ... and ugly underlining ... this is emacs -nw
> running in an xterm ... as you mentioned, hacking the xterm color scheme
> might be the way to go, but i haven't tried it yet ... turing up the heat
> on those primary colors is what i'm aiming for :-)

I see. Thanks you for sharing the screenshots. :)

-- 
Do not eat animals, respect them as you respect people.
https://duckduckgo.com/?q=how+to+(become+OR+eat)+vegan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2017-08-29 19:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 16:42 emacs -nw niggles Richard Banach
2017-08-26 13:12 ` Mario Castelán Castro
2017-08-29 13:04   ` Richard Banach
2017-08-29 13:14     ` Tim Visher
2017-08-29 13:36       ` Richard Banach
2017-08-29 13:43         ` Tim Visher
2017-08-29 13:53           ` Richard Banach
2017-08-29 16:38     ` Mario Castelán Castro
2017-08-29 17:12       ` Richard Banach
2017-08-29 19:06         ` Mario Castelán Castro [this message]
2017-08-30 13:49           ` Richard Banach
2017-08-30 14:16             ` Mario Castelán Castro
2017-08-30 14:51               ` Richard Banach
2017-08-30 14:53                 ` Mario Castelán Castro
2017-08-30 15:33             ` Tim Visher

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=2d0e8771-567c-4b9f-8840-cedb3ed7d2e1@yandex.com \
    --to=marioxcc.mt@yandex.com \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).