Hi,
I have:
(setq next-error-highlight 'fringe-arrow)
If I find error while compiling, next-error put a fringe arrow in the
error line. If I fix the error and compile again, the fringe arrow
does not dissapear (I do not if this is intended to be this way).
If the I open a gud session, I
Am 23.03.2005 um 01:58 schrieb Richard Stallman:
It is supposed to be a quick click only that will visit the
file. A long click should move point.
Doesn't it do that?
Yes, after I read about it, I found that it works exactly as described.
Since I stick to click-to-focus to have control to where
$B40A4L5NA3NDj!*!*!*(B
$B:#$^$G![EMAIL PROTECTED],(B
$B9%I$K$D$-!A49q3HBg!*!*:#$,%A%c%s%9$G$9!#(B
$B(%3%3$KEPO?$7$F$k=w$N;R$OK\Ev$G$9!#(B
1.$B5U!{=u4uK[EMAIL PROTECTED](B
2.$B#S#M4uK[EMAIL PROTECTED](B
3.$B:#F|[EMAIL PROTECTED](B
4.$BITNQ4uK[EMAIL PROTECTED](B
[EMAIL
Here's my take on this:
In the beginning there was just one overlay-arrow-position shared between GUD
and Edebug. Now there are more modes competing for it, there are conflicts.
Compilation modes, as you describe uses it in two places and tries to get
round the problem by making
Symptoms:
utf-8 chars doesnt work in todays emacs.
they show up as empty spaces.
I tried emacs -nw --no-init
and typed some swedish chars =8e5=8e4=8f6.
swedish chars do work at the shell prompt.
im running this on a redhat fedora core 2 gnu/linux box remotely over
ssh using the putty ssh w32
Symptoms:
When icomplete is switched on, it is a bit too intrusive:
On sending a bug report, the user is asked to put a bug description in
the subject. While the description is typed in, (No matches) is
displayed all the time. This is annoying because how can there be
matches?
In dired mode,
So, which terminal-coding-system should we set by default when LANG is
de_DE.UTF-8(en_US.UTF-8), iso-latin-1 or utf-8?
The terminal coding system does not necessarily depend on LANG.
It seems that OSX's Terminal.app uses utf-8 by default, independently from
any locale. Maybe it can be set to
I've got comment characters defined like this for tacl-mode
(modify-syntax-entry ?\~ / st) ; ~ gets Escape syntax
(modify-syntax-entry ?\{ st) ; comment start {
(modify-syntax-entry ?\} st) ; comment end }
(modify-syntax-entry ?\= _ b12 st) ; comment start ==
Title: 2887726
Browse
Search
Shop
My eSoft
Community
Back to Software Overview
Home
All Categories
Computers
Software
Operating Systems
Windows
Hi,
I have set
(setq next-error-highlight-no-select 2.0)
In the following please suppose that I have activated
`next-error-follow-minor-mode'.
If in a grep or compilation buffer I move the cursor, the hit location
buffer is shown in another window. Problem, IMHO, it that this window
seems to
(modify-syntax-entry ?\= _ b12 st) ; comment start ==
Yes, it seems the problem is that your 2-char comment sequence is made of
symbol-chars, so there are cases where the code does things like oh, here's
a symbol, let's skip it without checking whether some of the chars that
compose the
,-- On Wed, 23 Mar 2005 08:43:44 -0500, Stefan wrote:
|
| On sending a bug report, the user is asked to put a bug description in
| the subject. While the description is typed in, (No matches) is
| displayed all the time. This is annoying because how can there be
| matches?
|
| Sorry, I
JUAN-LEON Lahoz Garcia [EMAIL PROTECTED] writes:
(setq next-error-highlight-no-select 2.0)
In the following please suppose that I have activated
`next-error-follow-minor-mode'.
If in a grep or compilation buffer I move the cursor, the hit location
buffer is shown in another window. Problem,
Am 23.03.2005 um 19:52 schrieb Stefan Monnier:
Does the patch below help?
No. Still I have:
(Quellen/Emacs_CVS/emacs/src/emacs)
Loading disp-table...done
Loading encoded-kb...done
Sind jetzt in PETEs .emacs
but at least I can see my UTF-8 file names in dired
14 matches
Mail list logo
