public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Cary Jamison" <Cary_Jamison@Symantec.com>
To: cygwin-talk@cygwin.com
Subject: Re: copying and pasting in the terminal window?
Date: Tue, 29 Aug 2006 15:44:00 -0000	[thread overview]
Message-ID: <ed1n0r$m3j$1@sea.gmane.org> (raw)
In-Reply-To: <ecve93$rqt$1@sea.gmane.org>

mwoehlke wrote:
> Igor Peshansky wondered if Console is right for him?:
>> On Mon, 28 Aug 2006, Cary Jamison also discovered that Console
>> rocks!:
>>> mwoehlke extolled the greatness of Console, by Marko (*not* the
>>> CUI): I've just started playing with this, also...I like it!  I
>>> like tabs, too. And I like that my regular windows programs work as
>>> well, which is something that rxvt doesn't give me.
>>
>> Ah, but does it understand all the ANSI sequences?  And do
>> Ctrl-Space and Ctrl-C work properly in it?
>
> Which ANSI sequences? In general, it does everything the CUI subsystem
> does (because it is using a CUI under the hood). Ctrl-C WFM if you
> mean sending SIGINT (and it seems to understand 'stty intr <blah>',
> after which <blah> sends SIGINT and ctrl-C dings at me). Ctrl-space
> however seems to be the same as regular space.
>
> Since I'm not an emacs person (I think that's what we're talking
> about?), I'm not missing anything here...

I usually use xemacs in a separate window, so these things don't bother me, 
either.  But, it does have issues with xemacs -nw.  One annoying thing is 
that even if you have the menu bar hidden, m-f, m-e, m-h, etc., still pop up 
the menus instead of getting sent to the app.  I guess I could see where 
that could be useful, but when you're wrapping a console window you can't 
assume you can have any keys for yourself, or you need a way to turn on and 
off if they get passed through.


Cary



      reply	other threads:[~2006-08-29 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eckhf7$mmm$1@sea.gmane.org>
     [not found] ` <001601c6c7d5$de748ee0$020aa8c0@DFW5RB41>
2006-08-25 16:17   ` mwoehlke
2006-08-26  0:26     ` Gary R. Van Sickle
2006-08-28 15:26       ` mwoehlke
2006-08-28 17:13         ` Cary Jamison
2006-08-28 17:57           ` Igor Peshansky
2006-08-28 18:56             ` mwoehlke
2006-08-29 15:44               ` Cary Jamison [this message]

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='ed1n0r$m3j$1@sea.gmane.org' \
    --to=cary_jamison@symantec.com \
    --cc=cygwin-talk@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).