From: Samuel Wales <samologist@gmail.com>
To: Peter Dyballa <Peter_Dyballa@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: dirtrack (shell mode) not working
Date: Mon, 4 May 2009 15:03:19 -0700 [thread overview]
Message-ID: <20524da70905041503r4c7d4dcx21e5e942b07919dd@mail.gmail.com> (raw)
In-Reply-To: <C6A4809F-4E24-461C-B805-3DD945246418@web.de>
On Mon, May 4, 2009 at 12:51, Peter Dyballa <Peter_Dyballa@web.de> wrote:
> Your "manual matching" works on the cleaned static text data, while the mode
> in the buffer sees the text plus the ANSI Esc codes which are used
I don't think so. My manual matching works on the mode in the buffer.
Why would it be any different for the function?
> Yes, me too! I would like to have other colours used for the number plate of
> my car. There are other options to display information on a desktop.
That is a strange parody of emacs. Let's not fix anything ever?
>> The first variable sets a single color, while the second two, afaik, only
>> affect movement. Is that correct?
>>
>
> Esc[value;...;valuem sets a graphic mode (colour, intensity, blinking,
> reverse). The value 0 resets, the value 1 sets intensity. The foreground (3)
> colours yellow (3), magenta (5), and blue (4) are set.
That was not my question either. You mentioned 3 variables as
solutions. I do not see that they are solutions. If that is
incorrect, please kindly say how the last 2 variables solve the
problem in any way whatsoever, and how the first solves it completely.
I know what ansi colors do. That is not the question. The question
is what I -- or dirtrack -- are doing wrong in getting dirtrack to
work.
Thanks.
next prev parent reply other threads:[~2009-05-04 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 2:09 dirtrack (shell mode) not working Samuel Wales
2009-05-04 2:15 ` Samuel Wales
2009-05-04 8:53 ` Peter Dyballa
2009-05-04 16:44 ` Samuel Wales
2009-05-04 19:51 ` Peter Dyballa
2009-05-04 22:03 ` Samuel Wales [this message]
2009-05-05 8:11 ` Peter Dyballa
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=20524da70905041503r4c7d4dcx21e5e942b07919dd@mail.gmail.com \
--to=samologist@gmail.com \
--cc=Peter_Dyballa@web.de \
--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).