From: sous lesquels <a9f54d2@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
Date: Fri, 18 Jul 2014 20:35:00 -0000 [thread overview]
Message-ID: <CAHV8iDEPNf-ZFvdVBVw=KhrV5ZopObRhgd7iemDgx9wuWSXWdQ@mail.gmail.com> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E7ECECD@USA7109MB022.na.xerox.net>
> If you can wait for the digest, you can simply open the selected message from
> the digest and reply to that, and it will be threaded.
Using Gmail, it doesn't seem to offer a way to see them as separate
mails or reply to a particular one, though. Oh, well...
> If you can't wait, then read the message using your browser and click on the
> "Raw text" link near the top. The first line will say something like
> From cygwin-return-191383-listarch-cygwin=...
> Note the message number 191383.
> Then you send an empty message to cygwin-get.191383@cygwin.com and it will
> mail you back the specified message. You can then reply to it and your reply
> will be threaded.
Perfect, exactly what I was looking for. Agree it's not the most
direct method, but then again solves all the situations I could think
of requiring a physical email message that can be replied to.
Thanks for the tip Ken!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-07-18 20:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 20:10 sous lesquels
2014-07-16 20:30 ` sous lesquels
2014-07-17 2:13 ` Christopher Faylor
2014-07-17 8:24 ` Corinna Vinschen
2014-07-18 3:28 ` Warren Young
2014-07-18 14:48 ` sous lesquels
2014-07-18 15:51 ` Larry Hall (Cygwin)
2014-07-18 16:59 ` sous lesquels
2014-07-18 17:59 ` Christopher Faylor
2014-07-18 18:48 ` Nellis, Kenneth
2014-07-18 20:35 ` sous lesquels [this message]
2014-07-21 12:32 ` Nellis, Kenneth
2014-07-23 0:50 ` Christopher Faylor
2015-08-20 16:35 Sous Lesquels
2015-08-20 21:45 ` Warren Young
2015-08-20 22:21 ` Sous Lesquels
2015-08-20 22:36 ` Warren Young
2015-08-21 12:37 ` Sous Lesquels
2015-08-21 18:53 ` Warren Young
2015-08-21 21:41 ` Thomas Wolff
2015-08-24 12:08 ` Philip Daniels
2015-08-25 16:35 ` Sous Lesquels
2015-08-25 16:47 ` cyg Simple
2015-08-27 19:47 ` Sous Lesquels
2015-08-28 13:23 ` Larry Hall (Cygwin)
2015-08-28 14:05 ` Sous Lesquels
2015-08-28 18:50 ` Larry Hall (Cygwin)
2015-08-28 21:31 ` Sous Lesquels
2015-08-28 21:53 ` Warren Young
2015-08-28 23:24 ` Warren Young
2015-08-25 18:20 ` Andrey Repin
2015-08-27 20:00 ` Sous Lesquels
2015-08-28 14:48 ` Andrey Repin
2015-08-28 21:09 ` Sous Lesquels
2015-08-28 23:27 ` Andrey Repin
2015-08-20 22:35 ` Andrey Repin
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='CAHV8iDEPNf-ZFvdVBVw=KhrV5ZopObRhgd7iemDgx9wuWSXWdQ@mail.gmail.com' \
--to=a9f54d2@gmail.com \
--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).