From: Drew Adams <drew.adams@oracle.com>
To: goncholden <goncholden@protonmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Indentation with spaces
Date: Sun, 12 Jun 2022 02:21:00 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488961CB7C6A158B2EF59F5F3A89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <ZT2u3Kwt-rDao551oRwE1U2USVZdZsU-XjJ2o41NgTFGf0ToYQrCfpj3Sp8MlzHJlxbC8eFIElZQKncICFPj-RYQS7sAofxi23b-goHFJTQ=@protonmail.com>
> The problem is much more complicated, so it is
> taking long time for developers to understand
> the nature of legacy code. Have any of them
> really worked with legacy fortran code written
> by many people[?]. I mean real legacy from the
> late 1950's to late 1980's.
I can't speak for "developers". But I have - I've
worked with legacy Fortran code from the 50s, 60s,
70s, and 80s. I've even written some of it.
If you don't find your happiness with Emacs then
you might consider using another editor. I've
also used editors from that prehistoric period -
maybe one of those will be more to your liking.
I prefer Emacs, though TBH I haven't used it with
Fortran. But your mileage may vary. Fortunately
it's easy to return Emacs and get your money back.
Quick and easy. Actually, don't even bother to
return it.
> > The smart-ass kid showed a clenched fist to the
> > guru, and asked what was in the fist. The reply:
> > a bird. The kid asked whether it was alive or
> > dead. The reply: "That's up to you."
It really _is_ up to you. Nobody's forcing you
to find peace with Emacs, let alone to find your
happiness with it.
People here (and elsewhere, where you've apparently
repeated the same question) are just trying to help
you. Clearly they're not succeeding at that, which
I guess is too bad.
A horse can be led to water...
next prev parent reply other threads:[~2022-06-12 2:21 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 22:21 Indentation with spaces goncholden via Users list for the GNU Emacs text editor
2022-06-08 22:52 ` Skip Montanaro
2022-06-08 23:40 ` goncholden
2022-06-09 1:57 ` Skip Montanaro
2022-06-09 3:08 ` Emanuel Berg
2022-06-09 3:12 ` goncholden
2022-06-09 3:17 ` Emanuel Berg
2022-06-09 12:01 ` goncholden
2022-06-10 10:02 ` Emanuel Berg
2022-06-09 9:51 ` Skip Montanaro
2022-06-09 12:33 ` goncholden
2022-06-09 18:43 ` Lele Gaifax
2022-06-10 9:57 ` Emanuel Berg
2022-06-10 10:29 ` Emanuel Berg
2022-06-10 18:43 ` goncholden
2022-06-11 4:37 ` Christopher Dimech
2022-06-11 5:38 ` Emanuel Berg
2022-06-11 6:16 ` Christopher Dimech
2022-06-09 13:37 ` goncholden
2022-06-09 13:49 ` goncholden
2022-06-09 16:06 ` tomas
2022-06-10 10:08 ` Emanuel Berg
2022-06-10 9:45 ` Emanuel Berg
2022-06-10 17:57 ` goncholden
2022-06-10 18:08 ` tomas
2022-06-10 18:12 ` goncholden
2022-06-10 18:33 ` Emanuel Berg
2022-06-10 18:46 ` goncholden
2022-06-10 18:40 ` tomas
2022-06-10 18:53 ` Emanuel Berg
2022-06-10 19:05 ` goncholden
2022-06-10 19:27 ` goncholden
2022-06-11 0:56 ` goncholden
2022-06-10 18:29 ` Emanuel Berg
2022-06-09 13:27 ` Po Lu
2022-06-09 15:44 ` goncholden
2022-06-10 10:20 ` Emanuel Berg
2022-06-10 10:16 ` Emanuel Berg
2022-06-10 11:35 ` Po Lu
2022-06-10 18:26 ` goncholden
2022-06-11 0:57 ` Po Lu
2022-06-11 1:05 ` goncholden
2022-06-11 1:17 ` Po Lu
2022-06-11 1:33 ` goncholden
2022-06-11 1:36 ` goncholden
2022-06-11 7:38 ` Eli Zaretskii
2022-06-11 7:44 ` Emanuel Berg
2022-06-11 8:26 ` Eli Zaretskii
2022-06-11 7:57 ` goncholden
2022-06-11 8:27 ` Eli Zaretskii
2022-06-11 9:07 ` goncholden
2022-06-11 10:10 ` Eli Zaretskii
2022-06-11 15:43 ` [External] : " Drew Adams
2022-06-11 20:31 ` goncholden
2022-06-12 2:21 ` Drew Adams [this message]
2022-06-12 3:08 ` goncholden
2022-06-12 6:42 ` Eli Zaretskii
2022-06-11 1:49 ` Emanuel Berg
2022-06-11 2:05 ` goncholden
2022-06-10 23:01 ` Emanuel Berg
2022-06-11 0:00 ` goncholden
2022-06-11 7:31 ` Eli Zaretskii
2022-06-11 0:58 ` Po Lu
2022-06-11 1:41 ` Emanuel Berg
2022-06-09 19:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-06-09 20:16 ` [External] : " Drew Adams
2022-06-09 20:20 ` goncholden
2022-06-11 5:16 ` Emanuel Berg
2022-06-11 5:33 ` tomas
2022-06-11 5:44 ` Emanuel Berg
2022-06-11 5:51 ` goncholden
2022-06-11 15:43 ` Drew Adams
2022-06-12 4:45 ` RE: [External] : " Christopher Dimech
2022-06-13 5:04 ` [External] : " Emanuel Berg
2022-06-10 10:29 ` reinventing the wheel but not faculty, libraries (was: Re: Indentation with spaces) Emanuel Berg
2022-06-09 5:30 ` Indentation with spaces Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB5488961CB7C6A158B2EF59F5F3A89@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=goncholden@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).