all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Po Lu <luangruo@yahoo.com>
Cc: psainty@orcon.net.nz, Eli Zaretskii <eliz@gnu.org>,
	uzibalqa@proton.me, 58459@debbugs.gnu.org,
	stefankangas@gmail.com
Subject: bug#58459: Getting a fresh emacs session with no customisation
Date: Fri, 14 Oct 2022 21:40:41 +0200	[thread overview]
Message-ID: <trinity-bcc5d9e2-ff38-45de-9cbc-3d725df7e70d-1665776441064@3c-app-mailcom-bs09> (raw)
In-Reply-To: <87edva95z3.fsf@yahoo.com>


> Sent: Friday, October 14, 2022 at 8:14 PM
> From: "Po Lu" <luangruo@yahoo.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: uzibalqa@proton.me, "Eli Zaretskii" <eliz@gnu.org>, psainty@orcon.net.nz, 58459@debbugs.gnu.org, stefankangas@gmail.com
> Subject: Re: bug#58459: Getting a fresh emacs session with no customisation
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > The code to interface Emacs to X-based GUIs needs rewriting by an
> > expert, and has needed it for decades.
>
> Such a hypothetical rewrite (who wants to rewrite the 100,000-odd lines
> of code that are needed to work with modern X systems?) will probably
> not happen, given the amount of manpower we currently have at hand.
> Even if it does, it will not affect whether or not Emacs understands X
> resources.

The same conditions occur within the scientific community.  Almost
nobody is willing to perform serious work.  For instance, many things
considered modern today, if you look under the hood, you will find everything
is basically a wrapper around fortran work from the 60s.  Not much innovation
or scientific value since then.  Most work is cosmetic and mainly for entertainment.
The 60s and 70s were much more productive.

Have organised quite a few projects where the path was to rewrite.  But this does
not really fit in well these days, so unless things are marshaled by appropriate
individuals, it will continue be to as you say.



> > Until it gets that rewrite, changes in it are likely to break
> > something.
>
> This was almost certainly taken out of context.
>





  reply	other threads:[~2022-10-14 19:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12  0:09 bug#58459: Getting a fresh emacs session with no customisation uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12  9:51 ` Stefan Kangas
2022-10-12 12:52   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 12:56     ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 16:23       ` Stefan Kangas
2022-10-12 17:30         ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 21:11           ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 22:47             ` Phil Sainty
2022-10-12 23:16               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13  1:14                 ` Stefan Kangas
2022-10-13  2:02                   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13  3:01                     ` Stefan Kangas
2022-10-13 15:48                       ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 10:22                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:09                       ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:19                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:52                           ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:14                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:27                               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:19                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:36                                   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:56                               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:15                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 15:47                         ` Eli Zaretskii
2022-10-13 16:06                           ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 16:20                             ` Eli Zaretskii
2022-10-13 17:51                               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 18:35                                 ` Christopher Dimech
2022-10-14  8:14                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 19:40                                     ` Christopher Dimech [this message]
2022-10-13 16:36                           ` Christopher Dimech
2022-10-13 19:13                             ` Eli Zaretskii
2022-10-13 19:20                               ` Christopher Dimech
2022-10-13 10:30                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-bcc5d9e2-ff38-45de-9cbc-3d725df7e70d-1665776441064@3c-app-mailcom-bs09 \
    --to=dimech@gmx.com \
    --cc=58459@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=psainty@orcon.net.nz \
    --cc=stefankangas@gmail.com \
    --cc=uzibalqa@proton.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.