Also, here are some alternate versions of the fringe line-wrapping
indicator bitmaps:
(define-fringe-bitmap 'continued-line [96 16 8 8 72 80 96 120] nil nil 'bottom)
(define-fringe-bitmap 'continuation-line [8 16 16 16 18 10 6 30] nil nil 'top)
These are lighter-weight than the current defaults,
Juanma Barranquero <[EMAIL PROTECTED]> writes:
>> Once your code is fixed this is not needed any more. If the occur-hook is
>> expected to set-buffer in most/many cases, it might make sense, but
>> otherwise it doesn't.
>
> Well, I think it makes sense even if occur-hook is not expected to
> chang
Now, I can easily change my function to do the right thing, but I
still feel that `occur-1' should be fixed by using
`save-current-buffer' around the call to "(run-hooks 'occur-hook). The
rationale being that setting the modified flag to nil on the wrong
buffer can lead to data
>> Sounds like a serious bug. Such bugs can lead to loss of data.
> Does that mean that you agree that occur mode should run occur-hook via
No, it means I agree that your code is buggy and should thus be fixed.
> (save-current-buffer
> (run-hooks 'occur-hook))
Once your code is fixed this
And BTW, occur-mode is a major mode. Shouldn't it use run-mode-hooks?
It already does, to run occur-mode-hook.
occur-hook is different.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
It seems like a feature worth adding. However, is it really right
to modify next-line? It is not a scroll command.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
> RET nil RET" *every time* he starts Emacs without loading .emacs.
Are you speaking seriously here?
The "emacs -Q" scenario is not a normal use scenario, AFAIK, so its
convenience doesn't really matter that much. At least not nearly as much as
the convenience of the normal situation.
S
As I understand it such an implementation would not take advantage of
the new hardware that supports multi-threading, eg: multi-core x86
processors.
I am not sure that case is important, or that it would outweigh
the slowness of all variable accesses.
I don't think that Emacs will oft
There are other commands using `a' letter to read function names (like
`elp-instrument-function', etc.) where getting the default function name
from the current buffer would be useful too. So maybe it's better to
implement this in `call-interactively' for all commands using `a'?
T
> Are you speaking seriously here?
> The "emacs -Q" scenario is not a normal use scenario, AFAIK, so its
> convenience doesn't really matter that much. At least not nearly as much as
> the convenience of the normal situation.
Let's put it other way: even on normal situation, it seems safer to
mak
> It already does, to run occur-mode-hook.
> occur-hook is different.
Ah, you're right. Silly me.
--
/L/e/k/t/u
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
> No, it means I agree that your code is buggy and should thus be fixed.
Why was my function buggy? Where is it documented that occur-hook
functions should not change the current buffer? Is that a generic
requirement for hook functions?
In this particular case, if `occur-1' didn't set the read-on
> In <[EMAIL PROTECTED]> Richard Stallman wrote:
> BTW, FC4 eats the C-SPC key for the `iiimx' program which is the
> input method for (at least?) Japanese text by default, so I
> couldn't use C-SPC for `set-mark-command' in Emacs. Liang Zhao
> kindly told me that it can be so
I like to use Kim's fringe "buffer-boundary indicator" bitmap feature
(set with the variable `indicate-buffer-boundaries'), but the default
bitmaps are rather unpleasant for several reasons --
(1) They're quite "heavy", so tend to draw the eye too much. With the
fringe line-wrapping indicat
On 6/22/05, Juri Linkov <[EMAIL PROTECTED]> wrote:
> > Hmmm on the other hand, there's already a face `border', with a
> > different meaning (for setting the X border pixel color).
>
> Is it possible to reuse the same face for vertical divider with an
> additional spec like '(((type tty) :inherit
On 6/22/05, Gaëtan LEURENT <[EMAIL PROTECTED]> wrote:
> Maybe a more systematic way to proceed would be to disable NBSP-escaping
> in read-only buffers (but it could sometimes be confusing, too).
Yes, I think that would be a mistake. For better or worse, it really
does seem to be something which
On 6/22/05, Richard M. Stallman <[EMAIL PROTECTED]> wrote:
> Maybe it would be better to keep the face-name as `vertical-divider',
>
> I like "border" better than "divider".
Fair enough.
-Miles
--
Do not taunt Happy Fun Ball.
___
Emacs-devel mail
[EMAIL PROTECTED],A}$($F$-$^$7$?!#(B
$B$3$3?t%v7n$G#3#0Be(B, $B#4#0Be(B, $B$=$l0J>[EMAIL
PROTECTED],A}$($F$*$j$^$9!#(B
$B$$$m$$$mLu$"$j$J$N$+$bCN$l$^$;$s$N$G!"CK$H$7$F<[EMAIL
PROTECTED]"$k#3#0Be0J>e$N(B
[EMAIL PROTECTED];W$$!"$3$N%a!<%k$rAw$j$^$7$?!#(B
$B#P#C=i?4%a(B, $BD>EE8r49$b;
Maybe it would be better to keep the face-name as `vertical-divider',
and also change the name of the display-table slot to match (it's easy
to provide a backward-compatibility alias for that).
What do other people think?
I like "border" better than "divider".
_
Stefan Monnier wrote on 21 Jun 2005 23:30:07 +0200:
> It's a feature. I couldn't stand reading the NBSP-escaping in some French
> articles where half the spaces are NBSP. NBSP-escaping is good in
> prog-lang buffers, not in Gnus's artcle buffer.
That makes sense, but I'd rather have the NBSP e
Anyway, it seems pretty natural to offer minor modes with a
customizable default setting, and not all minor modes might be 100%
user-preference.
Minor modes are supposed to be used for user preferences. Things
which are not user preferences should be handled with variables that
are no
Hi everybody,
in a German newsgroup somebody asked if it would be possible to keep
the position of point fixed while doing vertical motion, i.e. to have
a behavior commonly referred to as scroll lock. Such a behavior can
be useful when you are primarily reading (in contrast to editing) a
file and
On 6/21/05, Stefan Monnier <[EMAIL PROTECTED]> wrote:
> I for one would be annoyed to have to re-specify in Emacs the options I've
> already set globally in my ~/.cvsrc.
You can always set `vc-cvs-global-switches' to nil in your .emacs. The
situation I'm trying to fix is precisely the one where t
> Sounds like a serious bug. Such bugs can lead to loss of data.
Does that mean that you agree that occur mode should run occur-hook via
(save-current-buffer
(run-hooks 'occur-hook))
?
And BTW, occur-mode is a major mode. Shouldn't it use run-mode-hooks?
--
/L/e/k/t
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> Apparently these timings are not very fixed. In a freshly started
> Emacs, my proposed version took 12 seconds (instead of earlier 23) and
> the abstract versions 40 seconds (instead of 51). This gives a
> mysterious gain of 11 seconds for both. But n
Dear Internet-user, The Internet-stock exchange " Mazafaka. CC " in partnership with " FDCservers. Net " call attention to you the huge list of the criminal goods and services on our joint the Internet-resource.
The introduction. How it was.
In the beginning of 2004 we Le Ministre and Render, fo
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> ring-ref does not rotate the ring, nor does it "exhaust" it. Maybe
> you mean `ring-remove', but that would force me to copy the ring first.
you're right. i was thinking destructively (been reading Il Signore
Degli Annelli, that's my excuse :-)... so
> In my `occur-hook' I have a custom function which does not save the
> current buffer,
Sounds like a serious bug. Such bugs can lead to loss of data.
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listi
>> I don't know if it is a bug or a feature,
It's a feature. I couldn't stand reading the NBSP-escaping in some French
articles where half the spaces are NBSP. NBSP-escaping is good in
prog-lang buffers, not in Gnus's artcle buffer.
>> I'd say it makes perfect sense to not escape special charac
Apparently these timings are not very fixed. In a freshly started
Emacs, my proposed version took 12 seconds (instead of earlier 23) and
the abstract versions 40 seconds (instead of 51). This gives a
mysterious gain of 11 seconds for both. But now my proposed version
runs 3.33 times faster than
> I was running "emacs.exe -Q" today and was puzzled to see that the
> output of `vc-diff' talked about "conflicting specifications of output
> style", until I remembered that I have an entry on ~/.cvsrc which
> says: "diff -u2", and the default style for VC is "-c".
> So the question is: why does
After thinking a bit more, the algorithm I propose to install (took 23
seconds in the test case) seems clearly superior over the one that
took 20 seconds. The reason is that my proposed algorithm is linear
in the _length_ of the ring, the 20 second algorithm is linear in the
_size_ of the ring. T
Paul Pogonyshev wrote on 21 Jun 2005 20:38:47 +0200:
> I don't know if it is a bug or a feature, but why would you possibly want
> to see non-breaking spaces in your messages? I sort of want to read my
> mail, not investigate the typographic peculiarities in it.
Well, I guess it's not a common
Thien-Thi Nguyen wrote:
an index of -1 returns the "oldest" element.
so you could just `(ring-ref ring -1)' until the
ring is exhausted, obviating both `nreverse' and
`var' reference, while keeping the abstraction.
ring-ref does not rotate the ring, nor does it "exhaust" it. Maybe
yo
Gaëtan LEURENT wrote:
> Hi,
>
> I noticed that when displaying messages in Gnus, the NBSP and soft-hypen
> are just displayed as normal space and hyphen instead of being prefixed
> with an escape character (or NBSP being displayed as underlined as in
> the recent CVS).
I don't know if it is a bug
"Richard M. Stallman" <[EMAIL PROTECTED]> writes:
> That would make the usual case much slower.
> I prefer the idea of swapping bindings on thread switches.
As I understand it such an implementation would not take advantage of
the new hardware that supports multi-threading, eg: multi-core x86
pro
> Hmmm on the other hand, there's already a face `border', with a
> different meaning (for setting the X border pixel color).
Is it possible to reuse the same face for vertical divider with an
additional spec like '(((type tty) :inherit mode-line-inactive))?
> The name `vertical-border' seems sli
Hi,
I noticed that when displaying messages in Gnus, the NBSP and soft-hypen
are just displayed as normal space and hyphen instead of being prefixed
with an escape character (or NBSP being displayed as underlined as in
the recent CVS).
Step to reproduce:
- Start emacs CVS with: emacs -Q -f gnus
>> I see there is a bug not caused by my patch:
>>
>> emacs -q -nw -rv
>>
>> sets the background mode to light on xterm. But since -rv switches
>> foreground and background, it should switch the background mode too
>> from light to dark on xterm.
>
> I think this is a bug.
There are also othe
>> A better way to do this is to change the interactive specification of
>> `debug-on-entry' to call `function-called-at-point'.
>
> How about this?
There are other commands using `a' letter to read function names (like
`elp-instrument-function', etc.) where getting the default function name
from
Juanma Barranquero wrote:
> - Also, capitalize the interactive messages "active alpha: " and
> "inactive alpha: " to "Active alpha: " and "Inactive alpha: " (it's
> customary on interactive prompt).
Why not an actual alpha character? :-)
--
Kevin Rodgers
Lars Hansen wrote on 21 Jun 2005 17:47:08 +0200:
> Start todays emacs with -Q and set scroll-conservatively to some
> non-zero number, say 1.
> Then type eg. M-x ABC. Now the minibuffer shows "M-x ABC" as expected.
> But if you type the Danish character A-ring (a capital A with a ring
> above) e
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> (defun ring-elements (ring)
> "Return a list of the elements of RING in order, newest first."
> (let (lst)
> (dotimes (var (ring-length ring))
> (push (ring-ref ring var) lst))
> (nreverse lst)))
an index of -1 returns the "oldest" ele
Drew Adams wrote:
1. "Save Buffer As" runs command `write-file'. Where's the beef - er -
"buffer"?
2. "Save (current buffer)" runs command `save-buffer'.
3. "Close (current buffer)" runs command `kill-this-buffer'.
4. "Revert Buffer" runs command `revert-buffer'.
It doesn't matter what command
Start todays emacs with -Q and set scroll-conservatively to some
non-zero number, say 1.
Then type eg. M-x ABC. Now the minibuffer shows "M-x ABC" as expected.
But if you type the Danish character A-ring (a capital A with a ring
above) everything seems to disappear from the minibuffer.
I am sorry
If the secondary thread modifies a global, make the copy then (Copy On
Write).
This would be difficult to implement, considering that a symbol's value
is normally kept in its value cell.
The interpreter would just have to keep a hashtable of hashtables;
primary key is the secondar
David Kastrup wrote on 21 Jun 2005 07:29:49 +0200:
> TeX-PDF-mode does not go through DVI. A different executable "pdftex"
> is employed that has its own set of primitive commands.
The most obvious difference is that when using TeX you can include ps
graphics but not pdf, and when using PDFTeX
Maybe it would be better to keep the face-name as `vertical-divider',
and also change the name of the display-table slot to match (it's easy
to provide a backward-compatibility alias for that).
What do other people think?
I don't like "divider" much.
was quadratic. It essentially does ring-length times an aref in
_vector_, which unlike checking the element at an average position in
a _list_, would not appear to be linear in the size of the vector.
If it is a vector, you're right, it isn't quadratic.
_
Richard Stallman <[EMAIL PROTECTED]> writes:
> `scroll-margin' has no effect when `show-trailing-whitespace' is true.
>
> Would you please send a self-contained test case?
Start emacs -Q
Visit a file that is larger than a screenful (say etc/NEWS).
M-x set-variable RET scroll-margin RET 3 RE
> > Perhaps the easiest fix is just define the constants yourself.
> I've done.
I'm not sure whether it would be better to protect these with #ifndef, i.e.
#ifndef LWA_ALPHA
#define LWA_ALPHA 2
#endif
Take a look at other potential redefinition on the sources to see
what's usually done.
A
On Fri, May 20 2005, Stefan Monnier wrote:
>> Do you find _this_ menu completely unusable, or menus in general? If
>> the former, then maybe it can be improved.
>
> This menu in particular.
> But I have no idea how to improve it, so AFAIC no change can make
> it worse: feel free to change it.
Ad
Thank you for your kindly advices.
At Mon, 20 Jun 2005 23:58:35 +0200,
Juanma Barranquero wrote:
> I'm using Visual Studio .NET 2003 and I'm getting "undefined
> identifier" errors for LWA_ALPHA and WS_EX_LAYERED. They are on
> WinUser.h, of course; I suppose it's a _WIN32_WINNT >= 0x0500 thing.
>
On 6/21/05, Mathias Dahl <[EMAIL PROTECTED]> wrote:
> > Another possible renaming I forgot to mention is "Split Window". The
> > window is not split to result in a single window with a
> > divider.
>
> I do not agree. "Split Window" is in my opinion a very good
> description of what that command d
Richard Stallman <[EMAIL PROTECTED]> writes:
> I tested this the other day too and was confuzzled (confused +
> puzzled). After a while I realized that it had to do woth
> font-lock-mode overriding my coloring.
>
> Perhaps those menu items should be disabled when Font Lock is enabled.
"Drew Adams" <[EMAIL PROTECTED]> writes:
> Another possible renaming I forgot to mention is "Split Window". The
> window is not split to result in a single window with a
> divider. "New Window" would be a better name for this menu item.
I do not agree. "Split Window" is in my opinion a very good
56 matches
Mail list logo
