On 11 feb 2005, at 05.20, Stefan Monnier wrote:
In configure.in, for powerpc-apple-darwin, I believe that "using fink
packages if available" should be removed. There is no use for that
(as far
as I know?) since the needed packages (I think it's only ncurses) are
part
of the normal development en
> In configure.in, for powerpc-apple-darwin, I believe that "using fink
> packages if available" should be removed. There is no use for that (as far
> as I know?) since the needed packages (I think it's only ncurses) are part
> of the normal development environment.
[...]
> Note the question mark
> I would like to change find-file-noselect-1, which is called by find-file.
> It would mean that if you visit a file that is part of the source code of
> the current GDB session, then you can set a breakpoint by clicking in the
> fringe. Pretty good huh! It could also mean that I've broken find-fi
>> Is this not something that could be served by a hook? Or _should_ be
>> served by a hook?
> Yes, that's good feedback. vc adds vc-find-file-hook to find-file-hook
> in vc-hooks.el. However, that file is built into Emacs through loadup.
> Where could I add such a hook, so that it would always b
Custom currently does not recognize variable aliases. We are planning
on replacing the user option `blink-cursor' with `blink-cursor-mode'
to get rid of a bug, get rid of no longer needed duplication and be
more standard. We plan to keep `blink-cursor' as an alias. So people
who have `(setq blin
> Where could I add such a hook, so that it would always be included?
Answering my own question: it can be added in gdb-ui.el. The following patch
is only for gdb-ui.el, but it adds a function to find-file-hook. I guess it
could still break find-file, if its not right.
Is it OK to install this?
> Is this not something that could be served by a hook? Or _should_ be
> served by a hook?
Yes, that's good feedback. vc adds vc-find-file-hook to find-file-hook
in vc-hooks.el. However, that file is built into Emacs through loadup.
Where could I add such a hook, so that it would always be incl
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> That is why I dislike a car with a dashboard that never let's me see
> anything; why I dislike car which requires my mechanic to purchase a
> special device to find out what is going on.
>
> The information should be readily available.
You can lo
Is this not something that could be served by a hook? Or _should_ be
served by a hook? After all, if gdb-mode wants to do this sort of
thing, mightn't others?
Sticking gdb-specific code in the basic find-file machinery seems
pretty ugly -- and if it's _really_ needed, at least make it a single
f
>From my previous reply:
My previously posted patch was indeed not very good. Among other
things `C-h v blinking-cursor-mode' did not find the defcustom. The
patch you proposed has a similar problem.
The last remark may have been a little bit confusing. Meant was:
finding the defcustom b
I propose the following minor "organizational" change to cus-start.el.
The undo-* variables are defined in undo.c. The current version gives
the impression that they are defined in alloc.c. I will install if
there are no objections.
===File ~/cus-start.el-diff=
**
I will install the following doc patch to autorevert.el if there are
no objections. The patch would be silly if the first line of the
docstring were clear enough without it. But I believe that it is not.
===File ~/autorevert-diff-b=
*** autorevert.el 29 Dec
In configure.in, for powerpc-apple-darwin, I believe that "using fink
packages if available" should be removed. There is no use for that (as
far as I know?) since the needed packages (I think it's only ncurses)
are part of the normal development environment.
The problem with using fink package
My previously posted patch was indeed not very good. Among other
things `C-h v blinking-cursor-mode' did not find the defcustom. The
patch you proposed has a similar problem. Also cus-start.el is meant
for variables defined in the C code. I believe that we should avoid
using it for Lisp variabl
IMO, the beauty of Customize is that it hides all the nitty gritty
details that no users (novices or experts) need to worry about.
Emacs describes itself as
extensible,
customizable,
self-documenting,
real-time,
display.
Nowadays, few environments work just on a lin
Jérôme Marant <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Kim F. Storm) writes:
>
>> Choosing a new numbering scheme has been discussed for years now,
>> without making any decisions on what to do.
>>
>> So for the moment, I simply decided to use 22.0.50 for the CVS
>> version as this is in a
I have found it difficult and time consuming to browse the code in cus*.el
and wid*.el. The code is surely complicated (at least I think it is) so it
is no surprise. However I wonder if I am missing something. Is there an easy
way to find out what is going to happen when a widget is created? Could
- Original Message -
From: "David Kastrup" <[EMAIL PROTECTED]>
> I am no Windows expert at all. My opinion, however, would be that the
> installer should be made available as soon as possible, probably in
> the Emacs archive.
>
> However, it should be possible to let it package the lates
> (custom-set-variables
> ;; ...
> '(baud-rate 38400)
... the above is a bad idea: it is not good elisp code ...
I am not going to say it is good code. (Your `setq' example is
better.) Unfortunately, that is what is currently written
automatically in one's .emacs f
[EMAIL PROTECTED] (Kim F. Storm) writes:
> Choosing a new numbering scheme has been discussed for years now,
> without making any decisions on what to do.
>
> So for the moment, I simply decided to use 22.0.50 for the CVS version
> as this is in accordance with the current numbering scheme, and a
Richard Stallman <[EMAIL PROTECTED]> writes:
> I believe the logical structure Miles first suggested (essentially the
> first
> one above) with the enhancement above with a single "Get All"-button is
> the
> best. It gives the possibility to preview the values before setting them.
>
Richard Stallman <[EMAIL PROTECTED]> writes:
> As I said, I'll use 22.0.50 when I change things later today.
>
> As my previous message on this topic says, I have not decided what
> scheme we will use for this. I mentioned two possible schemes that I
> think may be good.
>
> I am always a day
Richard Stallman <[EMAIL PROTECTED]> writes:
> > This is the wrong solution. The right solution for variables such as
> > minibuffer-prompt-properties is to set up a valid expression for its
> > standard value. It may be necessary to store the current default
> > value in a new v
Stefan Monnier wrote:
Well, maybe we can help, if you tell us what you know, ;-)
The mail you replied to was all I knew at the time. But here is a
distilled description of the problem (I've omitted the 1025 character
string):
ELISP> (setq str (string-to-multibyte <1025 ASCII character string>)
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> Customize is a can of worms. But the worms can improve the garden if
> handled rightly!
I don't see how the changes you suggest can be seen as an improvement.
Quite the opposite.
IMO, the beauty of Customize is that it hides all the nitty gritt
I would like to change find-file-noselect-1, which is called by find-file. It
would mean that if you visit a file that is part of the source code of the
current GDB session, then you can set a breakpoint by clicking in the
fringe. Pretty good huh! It could also mean that I've broken find-file, ju
This doesn't look like the right fix.
Normally, the caller would instead use `STRING_SET_UNIBYTE' after the
call
(or rather calls one of make_foo_string which does it for him) if
needed.
You are right, the problem is finding where this should be done :-)
Jan D.
_
>> This doesn't look like the right fix.
>> Normally, the caller would instead use `STRING_SET_UNIBYTE' after the call
>> (or rather calls one of make_foo_string which does it for him) if needed.
> You are right, the problem is finding where this should be done :-)
Well, maybe we can help, if you
Richard Stallman <[EMAIL PROTECTED]> writes:
> I believe that Emacs Setup Utilities for MS Windows now is
> nearly finished. There should of course be CVS for it and I
> wonder if it should go into Emacs CVS or somewhere else. What
> are your opinions about this?
>
> My person
Richard Stallman <[EMAIL PROTECTED]> writes:
> The Emacs manual uses [EMAIL PROTECTED], which does not need any new macro.
> Please switch to that in the Calc manual, and avoid the problem?
Done; although this will make the printed output look less nice.
__
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
...
> I did not know that LaTeX mode had been added.
Should this have been announced somewhere?
> But as I said, it is very convenient for those who write papers
> using LaTeX, as many do,
Yes. To give credit where it's due, this was suggested b
Richard Stallman <[EMAIL PROTECTED]> writes:
> The Emacs manual uses [EMAIL PROTECTED], which does not need any new macro.
> Please switch to that in the Calc manual, and avoid the problem?
The problem is that [EMAIL PROTECTED] has a half-graphical Logo when
typesetting with TeX. One should eith
> should show in the value window the humanly readable version of what
> is set, such as
> (custom-set-variables
> ;; ...
> '(baud-rate 38400)
> ;; ... )
Whether we want to teach users or not, the above is a bad idea: it is not
good elisp code and noone should write such a thin
It is rather unclean to have a defcustom inside a function.
Let's try to solve this1 some other way.
The conventional way to handle custom definitions for variables
that are defined too early to use defcustom is thru cus-start.el.
Could you make it work that way?
I see that, for variables set up
Does this fix it?
*** novice.el 10 Feb 2005 01:13:28 -0500 1.36
--- novice.el 10 Feb 2005 12:39:35 -0500
***
*** 41,50
"Function to call to handle disabled commands.
If nil, the feature is disabled, i.e., all commands work normally.")
(defvaralias 'disabl
This change looks reasonable to me. Does anyone see a problem with it?
2005-02-09 Kevin Rodgers <[EMAIL PROTECTED]>
* progmodes/compile.el (compilation-disable-input): New option.
(compilation-start): If it's non-nil, send an EOF to the process.
However, the code i
I believe that Emacs Setup Utilities for MS Windows now is nearly finished.
There should of course be CVS for it and I wonder if it should go into Emacs
CVS or somewhere else. What are your opinions about this?
My personal opinion is of course that it should be there before next
The Emacs manual uses [EMAIL PROTECTED], which does not need any new macro.
Please switch to that in the Calc manual, and avoid the problem?
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
> This is the wrong solution. The right solution for variables such as
> minibuffer-prompt-properties is to set up a valid expression for its
> standard value. It may be necessary to store the current default
> value in a new variable
or use a `valid-expression' property on
I got a crash in this code in set_iterator_to_next.
It happened when I did a query replace, replacing \223 with ".
IT_BYTEPOS (*it) += it->len;
IT_CHARPOS (*it) += 1;
xassert (IT_BYTEPOS (*it) == CHAR_TO_BYTE (IT_CHARPOS (*it)));
Unfortunately GDB got rather confused
As I said, I'll use 22.0.50 when I change things later today.
As my previous message on this topic says, I have not decided what
scheme we will use for this. I mentioned two possible schemes that I
think may be good.
I am always a day behind in responding to my email. As a result, it
can ea
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> Customize is a can of worms. But the worms can improve the garden
> if handled rightly!
>
> As others feared years ago, I now fear that some will come to depend
> on their .emacs file being written automatically by Customize.
So what?
> They wi
I believe the logical structure Miles first suggested (essentially the first
one above) with the enhancement above with a single "Get All"-button is the
best. It gives the possibility to preview the values before setting them.
Yes, it does that. However, it is also more cumbersome to
I am not sure whether
the change from S => F,C into S => F is a good idea.
Agreed. See proposal above.
What does "proposal above" refer to? I don't see anything
that appears to relate to this.
My bad. I read what you wrote backward, I guess. The proposal
Customize is a can of worms. But the worms can improve the garden if
handled rightly!
As others feared years ago, I now fear that some will come to depend
on their .emacs file being written automatically by Customize. They
will lose or not gain an understanding of the technology. This
applies e
"Robert J. Chassell" <[EMAIL PROTECTED]> writes:
> How can you save Customize settings without also setting their
> current values (today)? And, again, changing a value in your init
> file is not what is meant currently by "set"; "set" refers to
> setting the current values.
>
> Ju
... the current value is updated to the same value that is written
to your custom file. That is not the same thing as evaluating your
entire .emacs file, however.
I am refering to `All'. Clearly, individual settings should not
involve evaluating your entire .emacs file.
How can y
Richard Stallman <[EMAIL PROTECTED]> writes:
> [I sent this message twice but did not get a response.]
>
> Would someone please look at this and DTRT and ack? There is no
> particular maintainer of URL, but we need to fix the bugs.
> Would someone please fix this one?
>
> From: Klaus Straubinger
Why do we need to use @LaTeX{} in calc.texi? What's so important
about this macro that it must be used there?
It turns out that the maintainers of Calc mode added LaTeX to the
types of user visible output for which it can automatically write
mathematical expressions.
Thus, in addition to t
Jason Rumney <[EMAIL PROTECTED]> writes:
> Kim F. Storm wrote:
>
>>Miles recently enabled xassert unconditionally to catch undiscovered
>>bugs in redisplay and other places...
>>
>>We have now seen several crashes caused by this change -- but none of
>>them has been fully diagnosed yet, as this is
Kim F. Storm wrote:
Miles recently enabled xassert unconditionally to catch undiscovered
bugs in redisplay and other places...
We have now seen several crashes caused by this change -- but none of
them has been fully diagnosed yet, as this is very hard without having
easy ways to reproduce the cras
"Eli Zaretskii" <[EMAIL PROTECTED]> writes:
>> From: Nick Roberts <[EMAIL PROTECTED]>
>> Date: Thu, 10 Feb 2005 09:23:50 +1300
>> Cc: emacs-devel@gnu.org
>>
>> On a related note (or possibly unrelated), if you type "C-h i d m
>> elisp RET", then "i system-type RET", shouldn't you see the full
>>
Miles recently enabled xassert unconditionally to catch undiscovered
bugs in redisplay and other places...
We have now seen several crashes caused by this change -- but none of
them has been fully diagnosed yet, as this is very hard without having
easy ways to reproduce the crashes.
Debugging th
53 matches
Mail list logo
