From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] emacs 27.1-1
Date: Sun, 16 Aug 2020 14:38:46 +0200 [thread overview]
Message-ID: <87d03qrcix.fsf@Rainer.invalid> (raw)
In-Reply-To: <87y2mfktgv.fsf@Otto.invalid> (ASSI's message of "Sun, 16 Aug 2020 08:14:40 +0200")
ASSI writes:
> I haven't tried so-long-mode (it seems to have become available only
> with emacs-27), but it appears from its description that it would also
> DTRT in my particular case.
Now that I did try it: so-long-mode doesn't recognize the file I'm
testing it with aas problematic apparently. But I guess I'll have to
dig a bit deeper to see if that's what's happening or if it is something
else.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next prev parent reply other threads:[~2020-08-16 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 16:48 Ken Brown via Cygwin-announce
2020-08-15 15:07 ` Achim Gratz
2020-08-15 21:26 ` Ken Brown
2020-08-16 6:14 ` ASSI
2020-08-16 12:38 ` Achim Gratz [this message]
2020-08-16 6:06 ` ASSI
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=87d03qrcix.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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).