From: Peter Dyballa <Peter_Dyballa@web.de>
To: Samuel Wales <samologist@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: dirtrack (shell mode) not working
Date: Mon, 4 May 2009 21:51:16 +0200 [thread overview]
Message-ID: <C6A4809F-4E24-461C-B805-3DD945246418@web.de> (raw)
In-Reply-To: <20524da70905040944u31f648f8h71c17dfca3c654ec@mail.gmail.com>
Am 04.05.2009 um 18:44 schrieb Samuel Wales:
> On 2009-05-04, Peter Dyballa wrote:
>>> Input `cd ..
>>> [33m [0m [35m 03-Sun-19-12-32 [0m L4 [1;34m ~/Desktop/A$
>>> [0m ' failed to match `dirtrack-regexp'
>
> The big question here is why manual matching works perfectly fine.
> Why would ansi colors throw dirtrack off when regexp search backward
> accurately identifies the path and only the path?
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
>
> It would be a shame to get rid of the colors in the prompt, as they
> separate its components visually for me in a way that makes them
> easier to notice.
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.
> 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.
--
Greetings
Pete
"Debugging? Klingons do not debug! Our software does not coddle the
weak."
next prev parent reply other threads:[~2009-05-04 19:51 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 [this message]
2009-05-04 22:03 ` Samuel Wales
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C6A4809F-4E24-461C-B805-3DD945246418@web.de \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=samologist@gmail.com \
/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.