unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: larry liang <lrry05@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: viper mode macro broken when using '/' for search
Date: Thu, 9 Aug 2018 11:30:38 +0000 (UTC)	[thread overview]
Message-ID: <1662305111.4621790.1533814238536@mail.yahoo.com> (raw)
In-Reply-To: <65398357.4640245.1533814056004@mail.yahoo.com>

 Sorry, forgot to mention the version. This problem exists in both 25.x and 26.x, but works well in 24.x.
    On Thursday, August 9, 2018, 7:27:36 AM EDT, larry liang <lrry05@yahoo.com> wrote:  
 
 When recording a macro in viper mode, and type / for searching a string, the / character is included in the macro twice. For example, if I type:
/ abc
the record macro is: [ / / a b c ]  


  reply	other threads:[~2018-08-09 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <65398357.4640245.1533814056004.ref@mail.yahoo.com>
2018-08-09 11:27 ` viper mode macro broken when using '/' for search larry liang
2018-08-09 11:30   ` larry liang [this message]
2018-09-05 15:37     ` Stefan Monnier

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=1662305111.4621790.1533814238536@mail.yahoo.com \
    --to=lrry05@yahoo.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).