unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: ludvig-faddeev@gmx.com
To: Robert Thorpe <rt@robertthorpeconsulting.com>
Cc: help-gnu-emacs@gnu.org
Subject: define-key for fortran code
Date: Sat, 29 May 2021 18:39:59 +0200	[thread overview]
Message-ID: <trinity-d818706c-0f79-486b-8303-5a3b299bc6ac-1622306399440@3c-app-mailcom-bs01> (raw)
In-Reply-To: <874kelboti.fsf@robertthorpeconsulting.com>

There is not much information about how to set up fortran in emacs.  An added complication
is the various flavours of fortran (fixed format, free format, f95, f03, f08).  This is
making the fortarn language quite messed up, unlike what happened to C++ when new features
were added in. 

In this day and age of technology, pissing people off on the internet is not hard, and if
you’re really trying to get back at someone, this list is the most annoying with signs of
everyday people who just irk you by existing. 

Ludvig

> Sent: Sunday, May 30, 2021 at 2:24 AM
> From: "Robert Thorpe" <rt@robertthorpeconsulting.com>
> To: jaime-escalante@gmx.com
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: define-key for fortran code
>
> I'd just like to point out, that it is obvious that emails from several
> different addresses are coming from the same person.
> 
> The emails from the following addresses are all asking about the same
> features of Emacs in the same way....
> 
> jaime-escalante@gmx.com
> ludvig-faddeev@gmx.com
> michael-franzese@gmx.com
> pauline-galea@gmx.com
> 
> There is no point in doing that on this list.
> 
> It would help a lot if your questions were more specific and you explain
> what you are expecting to happen more clearly.
> 
> BR,
> Robert Thorpe
> 
>



  parent reply	other threads:[~2021-05-29 16:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 17:47 define-key for fortran code jaime-escalante
2021-05-29  4:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 12:13   ` ludvig-faddeev
2021-05-29 12:25     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 13:18   ` jaime-escalante
2021-05-29 14:24     ` Robert Thorpe
2021-05-29 14:32       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 16:55         ` pauline-galea
2021-05-29 20:03           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 16:39       ` ludvig-faddeev [this message]
2021-05-29 20:00         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 17:20       ` ludvig-faddeev
2021-05-29 20:04         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 17:44       ` Jean Louis
2021-05-29 20:06         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 14:37     ` Emanuel Berg via Users list for the GNU Emacs text editor

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=trinity-d818706c-0f79-486b-8303-5a3b299bc6ac-1622306399440@3c-app-mailcom-bs01 \
    --to=ludvig-faddeev@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rt@robertthorpeconsulting.com \
    /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).