My notion of a theme is not a named collection of configuration
settings. Rather it is an expression of high-level intent:
Aren't themes generally named collections of settings?
I thought that's what "theme" means.
- as much as possible behave like Window / MacOS / *nix
Maybe that c
I'm not enthusiastic about Aquamacs because it seems to be headed in
the direction of being an alternative to Emacs rather than a
contribution to it. You have a right to do this, but helping people
do this is not the main goal of Emacs development.
___
> However, as long as the (IMHO sensible) patches that Seiji Zenitani and
> I have provided (which only pertain to the OS X version) don't find their
> way into the core or get formally rejected with reasons given,
Mac-only patches are looked at only by the people that are interested
i
>> Those customization variables can have a default value that lets them
>> cause different behavior only when under the Aquamacs theme.
>>
>> So I don't see this as a principal problem once themes work properly.
> Yes, but what about re-definitions of existing functions?
> Defadvice them and put
On 7 Jul 2005, at 15:20, David Kastrup wrote:
Making this process a bit easier, making it easier for the user to
undo some of these new 'defaults' by defining groups of
customizations in themes would certainly be desirable.
In Aquamacs, this is already the case for many customizations.
For so
David Reitter <[EMAIL PROTECTED]> writes:
> I have implemented the single frame behavior (it takes more than
> OneonOne to do that), for example.
> And if I understand correctly what themes are supposed to do, I
> cannot but agree with you that the currently planned collections of
> customization
On Thu, 07 Jul 2005 14:17:52 +0200, Lennart Borgman wrote:
>I agree to whole message. I have written EmacsW32 just for this above.
>It would be better if this idea was merged into Emacs. I think however
>that it has to coexist with themes in some way and perhaps themes can be
>the underlying st
Much as I like the idea of prepackaged distributions for normal,
non-developer users, the problem I see with many "big" Emacs projects
(like TinyTools, CEDET, JDEE, etc) is that they are much of an
all-or-nothing. You install one of them, you are no longer in Emacs,
but someone'
On 7 Jul 2005, at 13:22, David Reitter wrote:
I have implemented the single frame behavior (it takes more than
OneonOne to do that), for example.
As I've been asked to clarify this: We define a range of additional
functions, such as one to delete a buffer when its window is deleted,
and d
On 7 Jul 2005, at 19:39, Robert J. Chassell wrote:
Quick question: does Aquamacs require changes in the C code for just
in the Emacs Lisp?
As stated in my original post: "we patch the c core".
But the vast majority of changes comes from .el packages (in site-
lisp). Other distributions such
d unloading redefinitions of standard
functions, as well as dealing with advice flexibly.
I don't think the task would be easy to come up with a good, general set of
theming constructs that would let people write modular, non-monolithic
custom versions of Emacs. But it would be great if it existed
Juanma Barranquero wrote:
On one hand, I think that's similar to what Luc was proposing for the
custom-themes issue.
Oh, thanks Juanma, sorry Luc.
On the other, that doesn't avoid what I'm complaining about: you
should be able to use a big package and decide which bits are useful
to you an
On 7/7/05, Lennart Borgman <[EMAIL PROTECTED]> wrote:
> A very, very wild idea, a save excursion for loading so to say: could
> all the setting and defining functions be defadviced during loading of
> such packages in such a way that they saved old states of symbols in a
> list called say "previou
Juanma Barranquero wrote:
I agree to whole message. I have written EmacsW32 just for this above.
Much as I like the idea of prepackaged distributions for normal,
non-developer users, the problem I see with many "big" Emacs projects
(like TinyTools, CEDET, JDEE, etc) is that they are much
> I agree to whole message. I have written EmacsW32 just for this above.
Much as I like the idea of prepackaged distributions for normal,
non-developer users, the problem I see with many "big" Emacs projects
(like TinyTools, CEDET, JDEE, etc) is that they are much of an
all-or-nothing. You install
John S. Yates, Jr. wrote:
My notion of a theme is not a named collection of configuration
settings. Rather it is an expression of high-level intent:
- as much as possible behave like Window / MacOS / *nix
- underline clickable links
I agree to whole message. I have written EmacsW32 just for
On 7 Jul 2005, at 11:53, John S. Yates, Jr. wrote:
Historically, the Emacs community has provided default behavior
that catered to its entrenched userbase. The answer to nearly
any suggestion that such behavior might be awkward / unfamiliar /
jarring to new users, especially those on platforms
On Thu, 07 Jul 2005 01:28:22 -0700, Edward O'Connor wrote:
>Here's one vote for leaving the default as it is. I love how Emacs
>is a consistent environment across the various operating systems it
>runs on, and would much prefer it for the default Dired behavior to
>continue to be the same across a
18 matches
Mail list logo
