unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: What does (looking-at "\\>") mean?
Date: Mon, 26 Jan 2009 08:00:10 +0100	[thread overview]
Message-ID: <87fxj6r1qd.fsf@tux.homenetwork> (raw)
In-Reply-To: a0a0cf140901251651k142533bn3f5d11ed833b86ad@mail.gmail.com

Wang Lei <wanglei.198112@gmail.com> writes:

> I searched in elisp-info, but forgot emacs-info. :( Now, I got it.
> Thanks for your all!
>
> On 1/25/09, weber <hugows@gmail.com> wrote:
>> From the emacs info on regexps:
>>
>> `\>'
>>      matches the empty string, but only at the end of a word.  `\>'
>>      matches at the end of the buffer only if the contents end with a
>>      word-constituent character.
>>
>> HTH
>> Hugo
>>
>> Wang Lei wrote:
>>> Hi, all.
>>>
>>> I copied a piece of code like this:
>>>
>>> (defun my-indent-or-complete ()
>>>   (interactive)
>>>   (if (looking-at "\\>")
>>>       (hippie-expand nil)
>>>     (indent-for-tab-command)))
>>>
>>> But, I can't figure out what this "\\>" means. Could someone give me a
>>> explanation ?

With this little function, you can understand what looking at does:

Write a word in scratch buffer and leave point at end of word, then do
M-x test-looking-at

Then put the point at the beginning of word and run again test-looking-at

,----
| (defun test-looking-at ()
|   (interactive)
|   (if (looking-at "\\>")
|       (message "There is nothing after point")
|       (message "there is something after point")))
`----



-- 
A + Thierry Volpiatto
Location: Saint-Cyr-Sur-Mer - France





  reply	other threads:[~2009-01-26  7:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5745.1232899168.26697.help-gnu-emacs@gnu.org>
2009-01-25 20:07 ` What does (looking-at "\\>") mean? weber
2009-01-26  0:51   ` Wang Lei
2009-01-26  7:00     ` Thierry Volpiatto [this message]
2009-01-27  2:20       ` Wang Lei
2009-01-25 15:38 Wang Lei
2009-01-25 16:52 ` Drew Adams

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=87fxj6r1qd.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.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).