From: "Gary R. Van Sickle" <g.r.vansickle@att.net>
To: <cygwin@cygwin.com>
Subject: RE: xterm and cut & paste
Date: Sat, 03 Jan 2009 12:06:00 -0000 [thread overview]
Message-ID: <94BC2B9600534068B82C82DD4FECC79F@DFW5RB41> (raw)
In-Reply-To: <495F4C7A.4020706@gmail.com>
> From: Andy Koppe
>
> Brian Salter-Duke wrote:
> > On Fri, 02 Jan 2009 06:56:23 +0000, Fergus
> >> Include -clipboard as an option for XWin.
> >> e.g.
> >> run XWin -clipboard -nolisten local -multiwindow 2>nul
> & and then
> >> selected text in xterm is automatically copied to the
> clipboard for
> >> onward pasting.
> >> Fergus
> >
> > Thanks for that. I find X very confusing and mainly just
> want a simple
> > xterm to run mutt, slrn and unix like-codes.
>
> Fancy giving MinTTY a try? It is (or at least attempts to be)
> compatible with xterm, but it's a native Win32 program, i.e.
> X is not required.
>
> http://code.google.com/p/mintty
>
> Andy
And best of all, it's MinTTY fresh, not MedicineTTY.
ME = STILL GOT IT. ;-)
PS: File drag and drop is total coolness. It pastes in a Win32 path though,
which a few Cygwin apps probably won't be able to handle. Here's a
two-for-one idea, free of charge:
- Add a setting where the user can set whether he wants Win32 or POSIXy
paths dropped.
- Add a context menu when you right-drop which allows you to "Drop path as
Win32" or "Drop path as POSIX".
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2009-01-03 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 6:57 Fergus
2009-01-02 22:10 ` Brian Salter-Duke
2009-01-03 11:31 ` Andy Koppe
2009-01-03 12:06 ` Gary R. Van Sickle [this message]
2009-01-03 15:10 ` Andy Koppe
-- strict thread matches above, loose matches on Subject: below --
2009-01-01 22:12 Brian Salter-Duke
2009-01-02 4:42 ` Christopher Faylor
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=94BC2B9600534068B82C82DD4FECC79F@DFW5RB41 \
--to=g.r.vansickle@att.net \
--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).