[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Compile issues

From: Daniel Pfeiffer
Subject: Re: Compile issues
Date: Thu, 1 Apr 2004 21:50:34 +0200

Saluton, Moin,

Dave Love <address@hidden> skribis:

> address@hidden (Daniel Pfeiffer) writes:
> >> I'm surprised it was installed if the normal user interface doesn't
> >> work.
> >
> > "Doesn't work" is an exaggeration.
> ??  You may disagree that C-x ` is the normal interface implied by the
> manual, but it clearly doesn't work.  I'm worried if it's non-trivial
> to make it work.

I had never said I couldn't make it work.  I was only discussing to find out
what exactly people wanted.  And by the time you wrote this, you'd already
been informed that it's solved.

> > A message labeled "info" is a clear statement that this is not
> > something to worry about.
> Maybe, but it doesn't mean I should ignore it if I want to make Emacs
> work.

Infos are all kinds of bla, like something creating a directory, or makepp
telling you it's reading a makefile.  You can go to these things if you want,
but that's not normally required.  If you generally want to go to these, set
the threshold as described in NEWS.

> > It's in NEWS now.  Btw. Emacs can customize groups, and then you can
> > comfortably browse all the options.
> I tried the Custom version information, which indicated no new options
> since Emacs 20, and apropos showed up nothing I searched for.

I'm not so good at custom, maybe I should tell it which options were added in
21.3.50.  Or should I make that 21.4, for whenever that may appear?

> >> Yes, but.  Several different packages in Emacs did that.  It appeared
> >> to be sanctioned for that reason.  If it was wrong, one would expect
> >> the first Emacs package that needed to do it to fix the issue.
> >
> > Some of them I can't test or do not even understand.  Their authors
> > and maintainers have repeatedly been asked to cooperate, but did not
> > respond.  So we decided to install this, so that someone who finds
> > something broken, can at least explain that.
> I was just trying to explain why telling people they were asking for
> trouble isn't very helpful.

I didn't say I wouldn't help, only that you ventured on a dangerous path.  Of
course it was hard to do better with the old mode.  That overfraught
compile-internal alone would have been enough reason to redesign compile :-}

> For instance, I'm not exactly a beginner
> and I recently contributed a Python mode which used
> `compile-internal'.  No-one asked me about that, although I understood
> it was to be installed, but hasn't been.

I'm only aware of the official one by Barry A. Warsaw & Tim Peters, which
doesn't have this problem.  While grep is very different, python may be called
in makefiles, so it should work out of the box.  And the Python messages I've
seen are covered, so why have an extra python-compilation-mode (which woud be
the modern alternative to compile-internal)?

> Has the maintainer been
> asked about the Erlang mode I'm trying to fix at present?

What's that?  I can find Erlang all over etags.c and as a symbol in
simula-mode, but nothing else.  Again, if it's a compiler or interpreter, we
should just add Erlang's messages to compilation-error-regexp-alist-alist.

> Obviously I
> understand the difficulty of knowing what you might break if you
> _have_ to make an incompatible change for some reason, and I'm trying
> to help, though that doesn't seem to be a very productive activity
> these days.

OK, so how precisely can I help you to help?

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

lerne / learn / apprends / läramå / ucz się    Esperanto:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]