Trying to rebuild NTEmacs today using MinGW I found that I needed to replace:
$(EMACS) $(EMACSOPT) -l autoload --eval '(setq generated-autoload-file
"$(lisp)/loaddefs.el")' -f batch-update-autoloads $$wins
with
$(EMACS) $(EMACSOPT) -l autoload --eval '(setq generated-autoload-f
Recent builds of emacs seem to almost "hang" whenever I visit a
makefile. Take, for example, lisp/makefile.in in this project. I
have to kill font lock with C-g and change to text mode in order to
look at it. I traced the problem down to the fact that I set
font-lock-support-mode in my .emacs
I am trying to get a clue as to how this stuff is organized so that I
can fix the problems described below. Thanks for your attention.
David Abrahams <[EMAIL PROTECTED]> writes:
> This concerns the one remaining problem with the ClearType patch I'm
> trying to clean up and
This concerns the one remaining problem with the ClearType patch I'm
trying to clean up and submit. I hope I don't seem too insistent, but
I've been trying to get a hint for about a week.
David Abrahams <[EMAIL PROTECTED]> writes:
> David Abrahams <[EMAIL PRO
David Kastrup <[EMAIL PROTECTED]> writes:
> David Abrahams <[EMAIL PROTECTED]> writes:
>
>> Richard Stallman <[EMAIL PROTECTED]> writes:
>>
>>> Some programs need two, some need one. We had a long discussion
>>> of this, and decided that
Richard Stallman <[EMAIL PROTECTED]> writes:
> Some programs need two, some need one. We had a long discussion
> of this, and decided that most users would expect a single click
> to follow a link or activate a button.
I hope that predictive decisions about what most users will expect may
be am
David Abrahams <[EMAIL PROTECTED]> writes:
> David Abrahams <[EMAIL PROTECTED]> writes:
>
>> I am seeing some minor artifacts that I don't know what to do about.
>> For example, when I backspace over these parens starting from the end
>> of the line,
David Abrahams <[EMAIL PROTECTED]> writes:
> I am seeing some minor artifacts that I don't know what to do about.
> For example, when I backspace over these parens starting from the end
> of the line, I end up with some small remnants of the background color
> emacs use
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> There seems to be an increasing trend to make Emacs look and act like
>> a web browser in all contexts, making it frustrating to use for text
>> editing purposes. Setting the point is basic functionality, and I
>> shouldn't have to cross my fingers, d
Eli Zaretskii <[EMAIL PROTECTED]> writes:
> David, if it is now clear to you, based on these and other comments
> from Jason, how to write an improved patch, please post it here and I
> will install it.
It's close, thanks.
> If you still have questions, please ask here.
I am seeing some minor a
[EMAIL PROTECTED] writes:
> Often things that are only defined for _WIN32_WINNT > 0x0400 are not defined
> in
> the mingw headers, so we need to provide our own definitions anyway. I do
> think
> it makes it easier for future developers if we use the standard constant names
> instead of inventin
Eli Zaretskii <[EMAIL PROTECTED]> writes:
>> From: David Abrahams <[EMAIL PROTECTED]>
>> Cc: emacs-devel@gnu.org
>> Date: Wed, 08 Jun 2005 11:46:58 -0400
>>
>> Sorry, but I have a lot on my plate, so once I start waiting a few
>> more days it'
Stefan Monnier <[EMAIL PROTECTED]> writes:
> This said, I hope some version of your patch will be installed because
> I find the truncation of anti-aliased glyphs (which I have noticed the few
> rare times I've used NTEmacs) isn't just ugly but makes the use of small
> fonts more painful (I love s
Eli Zaretskii <[EMAIL PROTECTED]> writes:
>> From: David Abrahams <[EMAIL PROTECTED]>
>> Date: Wed, 08 Jun 2005 09:45:16 -0400
>>
>> Sorry to be a pest, but as easy as it was, solving this problem did
>> take significant effort on my part.
>
> T
David Abrahams <[EMAIL PROTECTED]> writes:
> Anyway, please let me know if you want to take what I've done and
> massage it yourself or if you'd like me to make specific changes so it
> can be integrated into the Emacs sourcebase.
Sorry to be a pest, but as easy as it
Miles Bader <[EMAIL PROTECTED]> writes:
> On 6/7/05, David Abrahams <[EMAIL PROTECTED]> wrote:
>> Yes, if you're concerned about redrawing the minimum possible number
>> of characters on a line, you don't want to do that. I think that's a
>> n
David Abrahams <[EMAIL PROTECTED]> writes:
> David Abrahams <[EMAIL PROTECTED]> writes:
>
>> I have nothing to add to
>> http://lists.gnu.org/archive/html/emacs-devel/2004-12/msg00364.html
>> except that it's happening for me, too.
>>
>> Ide
[EMAIL PROTECTED] writes:
> Quoting David Abrahams <[EMAIL PROTECTED]>:
>
>> Incidentally, it seemed to work just fine for me if I remove the
>> checks for whether cleartype is enabled altogether, and just make the
>> width adjustments unconditionally.
>
>
Lennart Borgman <[EMAIL PROTECTED]> writes:
> David Abrahams wrote:
>
>>
>>>>Redirecting stderr works on COMMAND.COM as far as I recall.
>>>>
>>>>
>>>No, it doesn't. "foo 2>bar" is interpreted as `foo' c
David Abrahams <[EMAIL PROTECTED]> writes:
> I have nothing to add to
> http://lists.gnu.org/archive/html/emacs-devel/2004-12/msg00364.html
> except that it's happening for me, too.
>
> Ideas, anyone?
I would be very glad to help fix this one if someone could give me
I have posted a patch for support of ClearType here:
http://article.gmane.org/gmane.emacs.devel/38081
I hope someone will see fit to integrate it into the Emacs source
base.
Thanks,
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
___
Ema
Eli Zaretskii <[EMAIL PROTECTED]> writes:
>> Date: Sun, 5 Jun 2005 13:38:00 +0100
>> From: [EMAIL PROTECTED]
>> Cc: emacs-devel@gnu.org
>>
>> Redirecting stderr works on COMMAND.COM as far as I recall.
>
> No, it doesn't. "foo 2>bar" is interpreted as `foo' called with an
> argument `2' and its
[EMAIL PROTECTED] writes:
> Quoting David Abrahams <[EMAIL PROTECTED]>:
>
>> When ClearType
>> (http://www.microsoft.com/typography/cleartype/tuner/Step1.aspx) is
>> enabled on an NT build of Emacs, it's very common for emacs to "slice
>> off
[EMAIL PROTECTED] writes:
> Quoting David Abrahams <[EMAIL PROTECTED]>:
>
>> When ClearType
>> (http://www.microsoft.com/typography/cleartype/tuner/Step1.aspx) is
>> enabled on an NT build of Emacs, it's very common for emacs to "slice
>> off
When ClearType
(http://www.microsoft.com/typography/cleartype/tuner/Step1.aspx) is
enabled on an NT build of Emacs, it's very common for emacs to "slice
off" a few antialiased pixels on either side of a character's vertical
member. It happens especially in lines that are being typed. You can
see
Richard Stallman <[EMAIL PROTECTED]> writes:
> If I repeat the above process, but issue a build command that repeats
> 6 times, and then I hit `f4' *again* during compilation, the point
> moves to the 2nd error in the source window and then after only a very
> brief pause, jumps to
RMS: sorry for the duplicate; I had forgotten to send to the list as
well.
Richard Stallman <[EMAIL PROTECTED]> writes:
> Sometime in the past year or so compilation-mode started acting very
> strangely for me with a CVS-built emacs. First, if I use next-error
> while compilation is
I have nothing to add to
http://lists.gnu.org/archive/html/emacs-devel/2004-12/msg00364.html
except that it's happening for me, too.
Ideas, anyone?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
___
Emacs-devel mailing list
Emacs-devel@
Andreas Schwab <[EMAIL PROTECTED]> writes:
> David Abrahams <[EMAIL PROTECTED]> writes:
>
>> Okay, emacs appears to have the right mtime, although I have to have a
>> strange reading of the file-attributes doc in order to see it that
>> way:
>>
>>
David Abrahams <[EMAIL PROTECTED]> writes:
>> The problem will most likely occur at every DST change.
>
> Haven't had problems at DST boundaries in the past.
>
> Thanks anyway.
Problem solved. This was due to the stupid Borland C++ Builder X
installer which
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> Emacs diredit:
>> -r--r--r-- 1 dave root25944 05-25 20:28 index.htm
>> DIR /TW:
>> 05/25/2005 08:28 PM25,944
>> index.htm
>> CVS/Entries
>> /index.htm/1.216/Wed M
Andre Spiegel <[EMAIL PROTECTED]> writes:
> On Thu, 2005-05-26 at 08:28 -0400, David Abrahams wrote:
>
>> I'm on EST, which is GMT-05:00. Even if one of these is supposed to
>> be a GMT time it doesn't agree with either of the others. I'm using
>>
Andre Spiegel <[EMAIL PROTECTED]> writes:
> On Wed, 2005-05-25 at 21:10 -0400, David Abrahams wrote:
>
>> In recent CVS builds of emacs (on NT), when I do `C-x v v' on an
>> *unmodified* file under version control, and I get:
>>
>> File is edited but r
In recent CVS builds of emacs (on NT), when I do `C-x v v' on an
*unmodified* file under version control, and I get:
File is edited but read-only; making it writable
File is under version-control; use C-x v v to check in/out
The file was *not* edited, but emacs seems confused about that. I
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> I see a file labelled "need-merge", so I do `d E' and get:
>
> `d E' doesn't "merge" changes, it helps resolve conflicts that
> appeared during an earlier merge.
Right, I knew that, but I used it anyway.
> It's a common misunderstanding (i.e. a mis
Symptom:
I see a file labelled "need-merge", so I do `d E' and get:
`merge' is not applicable to any of the selected files.
So I enter the file's path explicitly and get:
Retrieving revision 1.36...
Fontifying msvc.jam.1.36<2>... (regexps..)
Retrieving revision 1.36... Done
Retrieving
Nick Roberts <[EMAIL PROTECTED]> writes:
> > Second, next-error used to cause the error in question to scroll to
> > the top of the *compilation* buffer's window, which made it very easy
> > to see what was going on. Now emacs just moves that buffer's point
> > without scrolling. Since the a
Sometime in the past year or so compilation-mode started acting very
strangely for me with a CVS-built emacs. First, if I use next-error
while compilation is still going on, I will often, after a moment or
two, see the point jump unpredictably in the file it takes me to.
Second, next-error used
38 matches
Mail list logo
