> Date: Thu, 19 May 2005 00:52:56 +0200
> From: Juanma Barranquero <[EMAIL PROTECTED]>
>
> Anyway: tiff_load is pushing EBX into the stack and getting a
> different EBX when poping it out at the end of the function!
Can you set a watchpoint on the address where EBX is saved on the
stack, and then
> A function which was in the previous release of Emacs is now gone,
> without ever being marked as obsolete in any released version of
> Emacs. To me, this seems like a Bad Thing. What the function did, or
> how external packages chose to use it, seem irrelevant.
The entry in subr.el suggeste
I believe that the following is a bug. I do not know enough about mode
line stuff to fix it myself:
ELISP> (format-mode-line '(10 "12" "34" "56"))
"123456"
ELISP>
I believe that the return value should have been:
"123456"
Sincerely,
Luc.
> This is crazy! The default value for `adaptive-fiill-regexp' matches the
> null string, so if I want to use `adaptive-fill-function', I've got to
> somehow clobber this regexp. Having done that, I would have to
> incorporate its functionality into my `adaptive-fill-function'. YUCK!!!
> Surely
The doc string for window-inside-pixel-edges says:
Return a list of the edge pixel coordinates of window.
(LEFT TOP RIGHT BOTTOM), all relative to 0, 0 at top left corner of frame.
RIGHT is one more than the rightmost x position used by text in window,
and BOTTOM is one more than the bott
> Would it be a good idea now to remove post-command-idle-hook from Emacs
> and its reference in follow.el?
>
> Yes, please do. run-with-idle-timer has existed since Emacs 19.31.
> and post-command-idle-hook has been obsolete since then.
I've done this. I also removed post-command-i
> In `lisp-font-lock-syntactic-face-function' the expression
> (eq n (or (get sym 'doc-string-elt) 3))
> causes to paint _every_ third string subexpression of a top-level
> expression with `font-lock-doc-face'. That's annoying in a number of
> cases like, for example, `define-abbrev'. Why not s
>I suggest to add a file variable to the NEWS file so that it is
>displayed as if `hide-body' (C-c C-t) has been called (probably with a
>comment how to expand the hidden sections). Such a change makes this
>file *much* more readable IMHO.
> I disagree. I believe that would be co
Richard Stallman <[EMAIL PROTECTED]> writes:
> I don't mean to sound hostile, but I don't see what is wrong with a
> simple user customization. I don't understand why you would make large
> changes to Emacs when you could simply change the offending face on your
> machine.
>
> I do
Hi Jérôme,
> Would anybody be kind to either consider or reject this small patch or
> maybe propose a better way to achieve the goal?
> I haven't read any comment so far.
>
> (Here is an update)
>
> Thanks in advance.
>
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
>> Jérôme Marant <[EMAIL PROTECT
> In <[EMAIL PROTECTED]> Richard Stallman wrote:
> Yesterday, I changed my mind and added the ``:group 'something''
> argument to every defgroup, defface and defcustom forms in which
> it hasn't been specified in Gnus (the changes will be propagated
> into the Emacs trunk after
And to fix the bug with the single-semi-colon we now introduce
yet-another-config-var that major modes have to set?
So as long as major modes aren't adjusted to also set
font-lock-comment-start-skip, users will see strange behaviors under some
"unusual" circumstances (i.e. only on 8 color ttys, on
I spotted a couple of cross references between manuals that need
updating for recent node renamings,
In man,
2005-05-17 Kevin Ryde <[EMAIL PROTECTED]>
* widget.texi (Basic Types): Update cross ref from "Enabling Mouse-1
to Follow Links" to "Links and Mouse-1" per recent lispref
I spotted some apparently broken info cross referencs in mh-e
defgroups,
* mh-e/mh-customize.el (mh-folder-selection, mh-inc, mh-letter,
mh-scan-line-formats): Corrections to custom-manual links.
I'm not certain about the mh-folder-selection change (the first in the
diff), but put
> Better to disable image support for MSVC builds than to try to hack
> things to work by introducing redundant variables to save the values
> of other variables in.
Perhaps; note that I didn't say it wasn't a hack. OTOH, I normally use
a MSVC build and certainly don't appreciate Emacs crashing on
> That's quite different from the Unix calling conventions on i386, where
> only EAX, ECX and EDX are call-clobbered.
I was wrong wrt the MSVC calling conventions. MSDN docs say:
All arguments are widened to 32 bits when they are passed.
Return values are also widened to 32 bits and returne
I don't mean to sound hostile, but I don't see what is wrong with a
simple user customization. I don't understand why you would make large
changes to Emacs when you could simply change the offending face on your
machine.
I don't think I am the only user who uses a console and finds
I'm sorry for insufficient information. It was caused by the
following form which didn't specify the parent group.
(defgroup smime nil
"S/MIME configuration.")
That ought to be fixed, and likewise any other defgroups that fail
to specify a parent.
Yesterday, I changed my m
Specifically, I looked at emulation/cua-base.el and emulation/cua-rect.el
In the first, years 2003 and 2004 have been _deleted_.
In the second, year 2004 has been _deleted_.
That seems strange to me too. Would whoever made this change please
explain the reasoning behind it?
Don'
What if 10 lines get changed in each year of (say) 2000-2005
inclusive? Each year, the changes are too small to be substantial. But
the net result is that the state of the code in 2005 differs
substantially from that of 2000 (by 60 lines in this example). How is
the copyright he
By the way, I noticed the new bytecomp doesn't warn to the
defcustom form in which the parent group is not specified.
Strange, I thought I had tested it on that case.
I fixed it now. Thanks.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
htt
> Is there any reason not to turn on global-font-lock-mode by
default?
>
> I will give it a try for a while and see what I think.
Could you please share your conclusions?
Initially I found some featurelets I did not like, so I changed them.
Now I like the feature. H
I expect to be able to get to any customization group by starting from
M-x customize RET and following the links. Groups that indeed don't
belong to any parent groups except `emacs' SHOULD have :group 'emacs.
I don't see what the problem is.
It is not right for these to be first-l
Thanks to the wonders of dynamic scoping this actually changes the
semantics subtly. In most cases you'll never be able to tell the
difference, but when higer-order functions are involved it can be a problem;
so if you do that, be careful.
We never told users it was ok to use thes
I guess we should reinstall unfocus-frame just so VM keep sworking.
We should write a comment saying the reason.
Eli, could you do this if no one else does it first?
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo
below is an untested patch that sets the evaporate property
for newly-made overlays. munge to taste, etc.
This sets the property to t.
That is not what we are looking for now.
The goal now is to *find* possible bugs.
The patch should set the property to something unusual (maybe
`never-se
Would it be a good idea now to remove post-command-idle-hook from Emacs
and its reference in follow.el?
Yes, please do. run-with-idle-timer has existed since Emacs 19.31.
and post-command-idle-hook has been obsolete since then.
___
Emacs-devel
> I think this is simply a new feature, not fixing a problem.
Sure, just like Unicode is a new feature.
Yes. We are not considering adding any further Unicode support into
the coming release.
1) A back button when describe-face is called from list-faces-display
to take it ba
crisp.el seems to be still using cua--standard-movement-commands which
was recently removed. Eg,
M-x cua-mode
M-x crisp-mode
=> Symbol's value as variable is void: cua--standard-movement-commands
I only noticed this when trying some autoloads, I don't use either
myself.
Juanma Barranquero <[EMAIL PROTECTED]> writes:
>
> So, I can apply the attached patch and at least stop Emacs from
> crashing on Windows, but I certainly would appreciate a more
> insightful analysis from the "people in the know" wrt image support
> and/or Windows.
Better to disable image support
Juanma Barranquero <[EMAIL PROTECTED]> writes:
> Now, when this happened before (with the local variable img) someone
> said that the MinGW libraries were not respecting calling conventions,
> but I'm not sure. Calling conventions for MSVC say that you cannot
> trust EAX, EBX, ECX, EDX, ESI, or ED
On 5/18/05, Glenn Morris <[EMAIL PROTECTED]> wrote:
> 5. Keep track of code deletions. If, at any point, enough code is
>deleted so that the only remaining changes from some past year are
>no longer significant, then that year should not appear in
>copyright headers from that point onw
$B"v!&!yL5NAEPO?%-%c%s%Z!<%sCf!y!&"v(B
$B!!$d$C$Q$j=P0)$&$J$i$46a=j$G2q$($kAjhttp://www.jumpb2.net/?imasugu
$B!!%3%3$K%"%I8x3+$GBT$C$F$$$k$46a=jL<$,$$$C$Q$$(B(o^$B"O(B^o)[EMAIL
PROTECTED]&!&(B
$BEPO?8e(B5$BJ,0JFb$K$46a=j$G2q$([EMAIL PROTECTED]>R2pCW$7$^$
Richard Stallman <[EMAIL PROTECTED]> writes:
> I agree, that seems incorrect. I guess whoever or whatever made the
> change needs to be educated. Who or what was it?
it was me. you (and anyone else so inclined) can help educate me by
editing admin/notes/years to correct the erroneous guideline
On 5/18/05, David Kastrup <[EMAIL PROTECTED]> wrote:
> Dan Nicolaescu <[EMAIL PROTECTED]> writes:
>
> > Am I the only one that finds the new makefile-shell-face annoying?
> >
I second this - i immediately customized them back to the old ones.
> Only if accompanied by new patterns that render the m
Dan Nicolaescu <[EMAIL PROTECTED]> writes:
> Am I the only one that finds the new makefile-shell-face annoying?
I am too...
> It is unnecessarily distracting with that "seashell1" background.
Especially on ttys, where it's actually almost white. Text is now
displayed as (almost) white on whit
Hi,
Would anybody be kind to either consider or reject this small patch or
maybe propose a better way to achieve the goal?
I haven't read any comment so far.
(Here is an update)
Thanks in advance.
Jérôme Marant <[EMAIL PROTECTED]> writes:
> Jérôme Marant <[EMAIL PROTECTED]> writes:
>
>> Hi,
>
Richard Stallman <[EMAIL PROTECTED]> writes:
> I would suppose this applies to everyone using a laptop.
Well, I have been using Emacs on laptops for years and never had this
problem. I suggest you revert your changes in Emacs and instead
customize the face in your local setup. Releasing Emacs 2
Dan Nicolaescu wrote:
> Am I the only one that finds the new makefile-shell-face annoying?
Emphatically not. I usually love electric fruit salad, but this is
awful.
> Do we really need new faces introduced at this point in the release
> process?
The answer can only be "no".
This "feature free
I'm trying to update the copyright in lisp/calendar, and am finding it
really tough to do a good job. FWIW, my algorithm is something like
this:
1. Make a CVS diff between 00:00 on January first of two consecutive
years.
2. Work out the "number of lines" changed, bearing in mind that
renam
A function which was in the previous release of Emacs is now gone,
without ever being marked as obsolete in any released version of
Emacs. To me, this seems like a Bad Thing. What the function did, or
how external packages chose to use it, seem irrelevant.
___
$B"v!&!yL5NAEPO?%-%c%s%Z!<%sCf!y!&"v(B
$B!!$d$C$Q$j=P0)$&$J$i$46a=j$G2q$($kAjhttp://www.jumpb2.net/?imasugu
$B!!%3%3$K%"%I8x3+$GBT$C$F$$$k$46a=jL<$,$$$C$Q$$(B(o^$B"O(B^o)[EMAIL
PROTECTED]&!&(B
$BEPO?8e(B5$BJ,0JFb$K$46a=j$G2q$([EMAIL PROTECTED]>R2pCW$7$^$
Dan Nicolaescu <[EMAIL PROTECTED]> writes:
> Am I the only one that finds the new makefile-shell-face annoying?
No. I found them a horrid surprise when opening a makefile the other
day. My current Emacs has that set of changes, plus the dubious
font-lock-negation-char-face, completely removed.
Thien-Thi Nguyen wrote:
> Glenn Morris <[EMAIL PROTECTED]> writes:
>
>> How is the copyright header supposed to deal with this kind of
>> gradual, cumulative change?
>
> does admin/notes/years (just installed) address this question?
A list of guidelines like this is clearly needed and should prov
For some time now, TIFF images do crash optimized MSVC builds of Emacs
when using the MinGW-supplied TIFF library.
The crash happens in image_spec_value(), but it all boils down to the
fact that on lookup_image(), after
img->load_failed_p = img->type->load (f, img) == 0;
the value of th
Juanma Barranquero <[EMAIL PROTECTED]> writes:
> And BTW, didn't Richard say many months ago that legally speaking,
> years should be spelled as whole? I mean, shouldn't that be:
>
> Copyright (C) 1997, 1998, 1999, 2000, 2001 [etc.]
Spelling the years out also looks much better.
Trying to keep t
Werner Lemberg wrote:
I suggest to add a file variable to the NEWS file so that it is
displayed as if `hide-body' (C-c C-t) has been called (probably with a
comment how to expand the hidden sections). Such a change makes this
file *much* more readable IMHO.
I disagree. I believe tha
Dan Nicolaescu <[EMAIL PROTECTED]> writes:
> Am I the only one that finds the new makefile-shell-face annoying?
>
> It is unnecessarily distracting with that "seashell1" background.
Oh good grief. Seems like a blind person's idea of a pun.
> Do we really need new faces introduced at this point
Glenn Morris <[EMAIL PROTECTED]> writes:
> How is the copyright header supposed to deal with this kind of
> gradual, cumulative change?
does admin/notes/years (just installed) address this question?
thi
___
Emacs-devel mailing list
Emacs-devel@gnu.or
But during migrating existing packages, the drawback has
been obvious: Everywhere there is the need of checking a command for
being remote or not, and then to call `process-file' or
`call-process'.
I can't see why you did that. If in a certain call you want
the file name handler t
Besides the strange updates to cua-base.el / cua-rect.el reported earlier,
I also noticed that in net/telnet.el, year 2004 was _changed_ into 2005.
But while there were changes in 2004, there are no changes in 2005.
I agree, that seems incorrect. I guess whoever or whatever made the c
[EMAIL PROTECTED] (Kim F. Storm) writes:
> Please clarify the policy by documenting the correct
> procedure in FOR-RELEASE.
if there are to be policy corrections, please also modify
admin/notes/years (just installed), since FOR-RELEASE has
more temporary nature.
thi
__
Askold <[EMAIL PROTECTED]> writes:
> Hey man, check out the discounts these guys are offering on enlarge
> patches!
>
> Steel Package: 10 Patches reg $79.95 Now $49.95 ! Free shipping too!
[...]
> Millions of men are taking advantage of this revolutionary new
> product - Don't be left behind!
D
On 18 May 2005, at 00:35, Denis Bueno wrote:
gcc -I/sw/include -L/sw/lib -fpascal-strings -fno-common -DMAC_OSX
-I../mac/src -DHAVE_CONFIG_H -I. -I../src
-I/Users/dbueno/download/cvs-trees/emacs/mac/../lib-src
-I/Users/dbueno/download/cvs-trees/emacs/mac/../lib-src/../src -g -O2
movemail.o pop.o
Running a command remotely is something like
ssh
whereas running a remote command locally is something like
scp /tmp/foo; /tmp/foo
If instead of "command" you say "executable", the distinction will be
clearer. I'd say the second example does not make sense wi
[EMAIL PROTECTED] (Kim F. Storm) writes:
> TO me, the recent updates seem to be a step backwards, rather
> than forwards, in terms of accuracy.
please see file admin/notes/years (just installed), which is the
basis for which these particular recent changes were made. i hope
that we can maintain
> And do _not_ do it before the release!
Well, changing argument names can be destabilizing. Changing
docstrings certainly is not.
--
/L/e/k/t/u
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinf
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> 2) Change the argument names to match the docstrings.
>> Pros: it is the cleaner way.
>> Cons: lot of change in the cl* files; less coherence between argument
>> names among functions.
>
> Thanks to the wonders of dynamic scoping this a
In `lisp-font-lock-syntactic-face-function' the expression
(eq n (or (get sym 'doc-string-elt) 3))
causes to paint _every_ third string subexpression of a top-level
expression with `font-lock-doc-face'. That's annoying in a number of
cases like, for example, `define-abbrev'. Why not simplify this
LEGAL NOTICE
The following message is an email sent to you by an
administrator of "PayPal.com".If this message is spam, contains abusive or other comments you find offensive please
contact the webmaster at the following address:
[EMAIL PROTECTED]
Message sent to you foll
> How about if you do whatever is best so as to use the best possible names
> in each function?
OK. That's even better. assuming there's no interest in maintaining
absolute argument-name consistency between functions (which doesn't
exist now, to be fair).
--
/L/e/k/t/u
> TO me, the recent updates seem to be a step backwards, rather than forwards,
> in terms of accuracy.
I didn't change it, so not sure what's happened, but in any case I
think the procedure is way too prone to error.
If, according to Richard, we must not only put *in* the years where
changes are
> ! ;; Copyright (C) 1997, 98, 99, 2000, 01, 02, 2005 Free Software Foundation,
> Inc.
And BTW, didn't Richard say many months ago that legally speaking,
years should be spelled as whole? I mean, shouldn't that be:
Copyright (C) 1997, 1998, 1999, 2000, 2001 [etc.]
--
/L/e/k
I suggest to add a file variable to the NEWS file so that it is
displayed as if `hide-body' (C-c C-t) has been called (probably with a
comment how to expand the hidden sections). Such a change makes this
file *much* more readable IMHO.
Werner
__
I just refreshed my emacs CVS workspace (2005-05-17) and built a new
Emacs on Mac OS X (Tiger). Opening a 249 line makefile causes Emacs to
hang for several minutes while fontifying. The mini buffer says:
Fontifying GNUmakefile... (regexps..)
If I wait long enough it finishes but thi
Hi!
Am I the only one that finds the new makefile-shell-face annoying?
It is unnecessarily distracting with that "seashell1" background.
IMHO it does not bring any useful visual information. In a Makefile
lines that start with an whitespace are either commands (and now
they are highlighted wit
> In <[EMAIL PROTECTED]> Richard Stallman wrote:
> I got many warnings when compiling Gnus. For instance:
> smime.el:123:1:Warning: defgroup for `smime' fails to specify containing
> group
> I think that is a real bug. This group should surely be put in
> a logical place in the hi
2) Change the argument names to match the docstrings.
Pros: it is the cleaner way.
Cons: lot of change in the cl* files; less coherence between argument
names
among functions.
3) Change the docstrings to match the argument names.
Pro: easy.
C
I got many warnings when compiling Gnus. For instance:
smime.el:123:1:Warning: defgroup for `smime' fails to specify containing
group
I think that is a real bug. This group should surely be put in
a logical place in the hierarchy.
I think there might be customization groups which
Thanks.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
One could argue that just calling `process-file' should be
sufficient. But it isn't for packages which still want to support
Emacs 21.
Backwards-compatibility is nice, but it is not the most important
thing.
> If `call-process' would be able to handle remote
> commands
If everyone is to busy with other things, could I use defadvice to
instrument the overlay functions instead?
I don't know to what extent that will work, but you could try it.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org
Steps to reproduce:
1. M-: (ido-mode 'buffer)
2. Note that C-x C-f is *not* bound to any ido stuff.
3. M-: (ido-mode 'both)
4. Note that C-x C-f *is* bound to ido stuff.
5. M-: (ido-mode 'buffer)
6. Note that C-x C-f is *still* bound to ido stuff.
Here's one solution:
Index: ido.el
==
Hi John and emacs-devel,
I'm trying to get Eshell working with a recent CVS snapshot, but I
don't know where to start looking for the cause of this one problem.
I'm not sure if it's reproducible, but here's what I'm experiencing:
When I type `M-x eshell RET ls RET', there's no output. Instead, t
> I think this is simply a new feature, not fixing a problem.
Sure, just like Unicode is a new feature.
> Emacs is not incomplete or broken without it.
Navigating the help buffer without a forward button is tedious. This
is a small patch.
> So please save it for after the next release.
You
> Kyle Jones' VM 7.19 (and prior) mailer has an (unfocus-frame) in its
> vm-window.el file, VM didn't like the 2005-05-01 CVS removal of
> unfocus-frame.
Since unfocus-frame does nothing but return nil, I don't know why it was
needed in the first place
> My local workaround was to comment out
FYI,
Kyle Jones' VM 7.19 (and prior) mailer has an (unfocus-frame) in its
vm-window.el file, VM didn't like the 2005-05-01 CVS removal of
unfocus-frame.
My local workaround was to comment out the (unfocus-frame) in my copy
of vm-window.el; which may not be an option to the average VM user.
I ju
Richard Stallman <[EMAIL PROTECTED]> writes:
> patches for you to try.
below is an untested patch that sets the evaporate property
for newly-made overlays. munge to taste, etc.
thi
___
*** buffer.c4 May 2005 22:10:14 - 1.479
FWIW,
On 3/7/05, Andrew Nesbit <[EMAIL PROTECTED]> wrote:
> I checked out Emacs from CVS today. The standard build is OK, but I'm
> trying to build it with make-package so that all files are contained in
> Emacs.app:
I tried the same thing. And I essentially the same result as Andrew.
gcc -I/sw/
> 2) Change the argument names to match the docstrings.
> Pros: it is the cleaner way.
> Cons: lot of change in the cl* files; less coherence between argument
> names among functions.
Thanks to the wonders of dynamic scoping this actually changes the
semantics subtly. In most case
Katsumi Yamaoka <[EMAIL PROTECTED]> writes:
> I think there might be customization groups which don't belong to
> any parent groups except `emacs'. Although it is possible to avoid
> warnings by adding the ``:group 'emacs'' parameters, I don't think
> it is useful especially for `defgroup'.
I ex
Following the recent discussions, I have now moved cua rectangle mark
command from S-return to C-return.
For non-window systems, one possible binding would be C-x return.
There are already mule commands on C-x C-m though, so I don't
know if that will be possible / acceptable...
--
Kim F. Storm
Richard Stallman <[EMAIL PROTECTED]> writes:
> Sorry for being too short. I wanted to say that there should be a
> general concept for running commands on remote hosts.
>
> I would not say that it is a priority for Emacs to have such a thing.
> I think it would be a difficult thing to do.
>> Just for the record, we have to distinguish the idea of running a command
>> remotely and running locally a remote command.
> You lost me there ... Can you give examples to show the difference?
Running a command remotely is something like
ssh
whereas running a remote command local
84 matches
Mail list logo
