[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58459: Getting a fresh emacs session with no customisation
From: |
uzibalqa |
Subject: |
bug#58459: Getting a fresh emacs session with no customisation |
Date: |
Thu, 13 Oct 2022 12:09:02 +0000 |
------- Original Message -------
On Thursday, October 13th, 2022 at 10:22 AM, Po Lu <luangruo@yahoo.com> wrote:
> uzibalqa uzibalqa@proton.me writes:
>
> > Fine, but when this happens on Trisquel, then it is a topic of concern.
> > Aren't
> > maintainers supposed to work together? Most times everybody works
> > independently
> > with almost no concern or collaboration.
>
>
> Users actually want the desktop environment to set resources that make
> applications match the system stylesheet.
>
> If you don't, remove the resources. We cannot make decisions for the
> Trisquel developers.
>
> > I wonder the rational behind considering x-resources as authoritative.
> > As you mentioned, these days x-resources are a rather esoteric feature.
> > Your design should be the other way round. With a flag
> > `enforce-x-resources'.
> > So one always gets vanilla emacs with no init file, or when the init file
> > does nothing, or something goes wrong. It is very easy to make an init file
> > fail when one is writing emacs functionalities and packages.
>
>
> Emacs is an X program, and good X programs respect resources set in the
> usual locations. It is a decades old convention.
You can't even tell me which process is producing them and where.
> > It is also an emacs bug from my point of view. Especially when you confirm
> > that x-resources are not used all that often anymore.
> No.
Emacs should take the user's setting in the init file rather than override them
with bullshit that you reckon has authority.
- bug#58459: Getting a fresh emacs session with no customisation, (continued)
- bug#58459: Getting a fresh emacs session with no customisation, Stefan Kangas, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, Phil Sainty, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, Stefan Kangas, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, Stefan Kangas, 2022/10/12
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, Po Lu, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation,
uzibalqa <=
- bug#58459: Getting a fresh emacs session with no customisation, Po Lu, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, Po Lu, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, Po Lu, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, Po Lu, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, Eli Zaretskii, 2022/10/13
- bug#58459: Getting a fresh emacs session with no customisation, uzibalqa, 2022/10/13