SUMMARY: Re: SUMMARY: Wacky VI/VIM Problem on Solaris

From: Sun Manager (sunmngrs_at_mzserver.com)
Date: 10/29/03

  • Next message: V AS: "Re: I/O error on /export/home"
    To: <sunmanagers@sunmanagers.org>
    Date: Wed, 29 Oct 2003 16:07:46 -0500
    
    

    My apoligies: Martin Schmitt was had the correct answer -- basically
    when using vim, put into your .vimrc file:

    set cpoptions-=x

    Here is his full response (thanks Martin!):

    http://vimdoc.sourceforge.net/dion/vimum.html
    ------snip------
    CANCELLING

    You thought of executing a : or / command, but changed your mind. To
    get rid of what you already typed, without executing it, press CTRL-C or
    <Esc>.

            Note:
            <Esc> is the universal "get out" key. Unfortunately, in the
    good old
            Vi pressing <Esc> in a command line executed the command! Since
    that
            might be considered to be a bug, Vim uses <Esc> to cancel the
    command.
            But with the 'cpoptions' option it can be made Vi compatible.
    And
            when using a mapping (which might be written for Vi) <Esc> also
    works
            Vi compatible. Therefore, using CTRL-C is a method that always
    works.

    If you are at the start of the command line, pressing <BS> will cancel
    the command. It's like deleting the ":" or "/" that the line starts
    with.
    ------snap------

    To disable this behaviour, put the following into your ~/.vimrc:

    set cpoptions-=x

    > On a related note, the behavior of backspace is different on Solaris
    > than linux as well.

    Have you already run "stty erase <BS>" with <BS> being an actual press
    of the backspace key? If you always come from the same terminal, put
    this into your .profile and you should be fine.
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: V AS: "Re: I/O error on /export/home"

    Relevant Pages

    • Re: Problems installing XP SP2!
      ... package source directory and make sure the that XPSPS2sms.exe file exists in ... in your SMS Program command line property. ... > Executing program as a script ... > OnOptionalExecutionRequests failed for program Automated upgrade from XP ...
      (microsoft.public.sms.admin)
    • Re: Windows update error 0x80242008
      ... 2.219: Hotfix started with following command line: /si ... Unexpected Error While Executing Line 1 ( ... Test.IE7InstallBlock.Section) of PreRequisite ...
      (microsoft.public.windowsupdate)
    • RE: Open Form Code
      ... I've generally found that if you issue a DoEvents command after opening the ... I set that form's VISIBLE property to FALSE. ... VISIBLE property to TRUE immediately prior to executing the code. ...
      (microsoft.public.access.formscoding)
    • Re: Problem with Sql Server
      ... The sproc returns data ... > - Executing the command as an sproc by passing the sproc name and the ... > - Executing the command using CommandType.Text and passing the same string ... > - Running both web server and db server on same machine. ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: commands not waiting, /wait not helping
      ... > When executing an application that is a 32-bit GUI application, ... > the command prompt. ... > having a exe pathname with embedded spaces that needed to be in quotes. ... and wise needs to see switches before the scriptname. ...
      (microsoft.public.win32.programmer.tools)