Usually with :entry-format and :format.
No special formatting should be necessary, just to be able to use a simple
tag. I don't believe that was why :*format were introduced.
You would have to specify what a simple tag is in the first place.
Formatting tags is for handling non-standard cases
From: Zhang Wei [EMAIL PROTECTED]
Date: Sat, 23 Dec 2006 15:17:43 +0800
D:\download\emacs-gbk\ntmake bootstrap
mkdir oo-spd
mkdir oo-spd/i386
echo oo-spd/i386 stamp_BLD
', needed by `addsection'. Stop.`oo-spd/i386/addsection.exe
D:\download\emacs-gbk\nt
Thanks for reporting.
I
Eli Zaretskii [EMAIL PROTECTED] writes:
I cannot reproduce this on my machine. Is this the CVS code (and if
so, when did you checkout), or the 22.0.92 pretest?
The CVS code, updated.
Also, what versions of Make and shell (if any) did you use in this
build?
D:\download\emacs-gbk\ntmake -v
From: Zhang Wei [EMAIL PROTECTED]
Date: Sat, 23 Dec 2006 18:24:30 +0800
D:\download\emacs-gbk\ntmake -v
GNU Make 3.80
I don't recommend this version for building the Windows port. Can you
upgrade to Make 3.81? Note that nt/INSTALL says in its compatibility
table:
Lennart Borgman wrote:
With MSYS I get some very strange problems:
MSYS /c dir Pr*
MSYS /c dir Pr]
The above seems to be trouble because I tested different keyboards in
XP. I forgot to turn the keyboard switching characters off in XP.
If I try to enter * (see above) I get a ].
Start a fresh emacs --no-init-file. Load file foo.f (fortran-mode):
cat foo.f EOF
C This is a fortran comment
CALL FOO
EOF
On line 1 execute fill-paragraph, which will run
fortran-fill-paragraph. This gives me
C This is a fortran comment ALL FOO
In GNU Emacs 22.0.90.2
Forward and backward regexp search are not symmetrical.
This is explained in the Lisp Manual.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
2. Displaying one line of warning message for each rebound key
sequence is really annoying. We should just highlight them in a
different face and display the message in a tooltip, and/or when
the text is clicked on. After all, there is already a big warning
On that note I was wondering if there was any option to have emacs make more
backup files. It seems it only does so when I first save the file after
visiting it. But I normally only start a new Emacs when it crashes or I have
to reboot my machine which isn't very often. So I end up
On the other hand I would perhaps prefer it in a node on its own right
after Intro, something like Emacs and the platform GUI. This could
list all the subtle differences.
If we were to have a node about this, it certainly should not come so
early. It is a terrible annoyance for a
I put in those documentation fixes. Thanks for reminding me.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
A problem that causes loss of work is a serious problem. How to
address this one will take some thought, because each of these changes
has a good reason individually.
I just got bit by this and I bet others will too. In previous versions of
Emacs C-x C-v (find-alternate-file) used to
- They are apparently not autoloaded, so `C-h v' doesn't
recognize them until customize has been loaded.
How can `C-h v' help you to find something you're not aware of?
That's not the point. The point is that these should be well
documented, and autoloaded so you can get to
Usually with :entry-format and :format.
No special formatting should be necessary, just to be able to
use a simple tag. I don't believe that was why :*format were
introduced.
You would have to specify what a simple tag is in the first place.
I would? My bug report was clear
So? Bug reports about customization don't concern such users, so ignore them
in the present context. If you don't care about customization either, then
perhaps someone else should respond to this bug report. I do care about
customization, and that's why I reported the bug.
Sorry. I herewith
Richard Stallman [EMAIL PROTECTED] writes:
2. Displaying one line of warning message for each rebound key
sequence is really annoying. We should just highlight them in a
different face and display the message in a tooltip, and/or when
the text is clicked on.
Kevin Gallagher wrote:
I just got finished reading through this thread and, I must say, I'm a
bit puzzled by its continued limited focus to the question of To
backward slash or not to backward slash? in an Emacs shell window
running cmd.exe (or equivalent) on w32. Instead, this discussion
...And unfortunately it is a bug on w32, that in one sense is a
platform where we want to attract people because it makes it easier to
switch to GNU/Linux later.
Is that really the aim of Emacs on Windows? Presumably it could also make
GNU/Linux users feel more comfortable on
Nick Roberts wrote:
...And unfortunately it is a bug on w32, that in one sense is a
platform where we want to attract people because it makes it easier to
switch to GNU/Linux later.
Is that really the aim of Emacs on Windows? Presumably it could also make
GNU/Linux users feel
In that case, is there anything more to change?
Perhaps an xref from the Windows appendix to Symbol Completion?
Please do that if you want to.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
- None are mentioned in the Emacs manual (or the Elisp manual, for that
matter), so a user is unlikely to know about them.
We do not aim to mention all options in the manual.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
They are customizable, so users should be able to find them.
Why would they look for them if they are not aware of them, to use your
logic?
If you want to change things about a certain feature (such as the
custom buffer interface), you look at its custom group and see
what's
They are customizable, so users should be able to find them.
Why would they look for them if they are not aware of them,
to use your logic?
If you want to change things about a certain feature (such as the
custom buffer interface), you look at its custom group and see
what's
- None are mentioned in the Emacs manual (or the Elisp
manual, for that
matter), so a user is unlikely to know about them.
We do not aim to mention all options in the manual.
Of course not, and these probably need not be in a manual. My point was that
if they are not autoloaded
Richard Stallman [EMAIL PROTECTED] writes:
That man page is written in doc rather than in an.
Can we make woman detect use of the doc macros
and give a meaningful error message?
I checked in the test suggested by James Cloos.
___
From: Richard Stallman [EMAIL PROTECTED]
CC: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
Date: Sat, 23 Dec 2006 15:14:50 -0500
On the other hand I would perhaps prefer it in a node on its own right
after Intro, something like Emacs and the platform GUI. This
Eli Zaretskii [EMAIL PROTECTED] writes:
How did this happen? Did you checkout the CVS tree with the -kb
option to cvs up or cvs co? If not, some of your files in the nt/
subdirectory might have strange line endings. Can you please take a
closer look at nt/makefile.w32-in and the file
I just got bit by this and I bet others will too. In previous versions
of Emacs C-x C-v (find-alternate-file) used to prompt you if you hadn't
saved the work in the current buffer and you used to have to press 'y'
to discard it. *Now* it prompts you asking if you want to
28 matches
Mail list logo
