emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Jan Böcker" <jan.boecker@jboecker.de>
To: Herbert Sitz <hsitz@nwlink.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: tab visibility cycling doesn't work over putty/ssh with viper-mode enabled
Date: Thu, 20 May 2010 21:41:07 +0200	[thread overview]
Message-ID: <4BF59053.5080204@jboecker.de> (raw)
In-Reply-To: <loom.20100520T061030-431@post.gmane.org>

On 05/20/2010 06:14 AM, Herbert Sitz wrote:
> Herbert Sitz <hsitz <at> nwlink.com> writes:
>>
>> With viper-mode enabled all I get is a bell when I click on tab to cycle the
>> visibility of a heading in viper's normal mode.  
>>

Hi Herbert,

I could not reproduce this here (Ubuntu 10.04 host, Putty on Windows 7).
I have no experience with viper-mode and only know very basic vi
commands. When viper-mode asked me for  a user level, I specified 5.

Org-mode version 6.36trans (release_6.36.52.geec2)

Visibility cycling with TAB works both in command and insert mode.
I can also access the agenda using C-c a a.

Looks like putty is misconfigured. While quickly scanning through
putty's configuration menu, the only setting I noticed was "Connection
-> Data -> Terminal-type string", which is set to "xterm" here.

However, I did not modify the default values, so it should work out of
the box.

You can try logging in with putty, executing "sleep 5", and interrupting
that with C-c. If that does not work, the problem is definitely not
emacs related.

HTH, Jan

  reply	other threads:[~2010-05-20 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20  2:42 tab visibility cycling doesn't work over putty/ssh with viper-mode enabled Herbert Sitz
2010-05-20  4:14 ` Herbert Sitz
2010-05-20 19:41   ` Jan Böcker [this message]
2010-05-21 21:02     ` Herbert Sitz
2010-05-22  4:42       ` Herbert Sitz
2010-05-22 11:46         ` Jan Böcker

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BF59053.5080204@jboecker.de \
    --to=jan.boecker@jboecker.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=hsitz@nwlink.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).