all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dieter Wilhelm <dieter@duenenhof-wilhelm.de>
Cc: Peter Dyballa <Peter_Dyballa@Web.DE>,
	GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Quoting style of arguments etc. [was: multiline regex mode?]
Date: Sat, 25 Nov 2006 11:11:06 +0100	[thread overview]
Message-ID: <874psn25vp.fsf_-_@hans.local.net> (raw)
In-Reply-To: <103FCBBB-B642-4856-A110-1ED739CFDAAE@easesoftware.com> (Perry Smith's message of "Fri\, 24 Nov 2006 21\:32\:22 -0600")

Perry Smith <pedz@easesoftware.com> writes:

>           So "{[^}]*}" stands for 'a region that starts with `{´ and has no `}´ until the final `}´ is hit; between both braces any number (starting
>      with 0) of any character except `}´ can appear.'
>
> I don't quite understand why this should be in an "emacs" FAQ or wiki.  Its basic regular expressions.  One such document is here:
>
> http://en.wikipedia.org/wiki/Regular_expressions#Syntax
>

It's even nearer at hand:
C-h i g "(Emacs)Regexps" or `(Elisp)Regular Expressions'

While we are at it: Is there an accepted quoting style for arguments
etc.?  For example:

1. In the above case expressing the need for pressing keys and
   distinguishing between textual arguments for the minibuffer: "" or
   `' or something else?

2. In the comment string of functions when expressing also key
   bindings and subsequent command names: "Please type `M-x
   function-name'" or "Please type \"M-x function-name\""?

I can't remember there is something in the Elisp manual for coding
conventions.

-- 
    Best wishes

    H. Dieter Wilhelm
    Darmstadt, Germany

  reply	other threads:[~2006-11-25 10:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09 12:57 multiline regex mode? Giles Chamberlin
2006-10-13 20:02 ` Dieter Wilhelm
     [not found] ` <mailman.8131.1160774366.9609.help-gnu-emacs@gnu.org>
2006-10-16 10:20   ` Giles Chamberlin
2006-10-16 11:24     ` Michaël Cadilhac
     [not found]     ` <mailman.8206.1160997864.9609.help-gnu-emacs@gnu.org>
2006-10-16 15:42       ` Giles Chamberlin
2006-11-23 19:25 ` Stefan Monnier
2006-11-24 21:14   ` Dieter Wilhelm
2006-11-24 22:51     ` Peter Dyballa
2006-11-25  3:01       ` Dieter Wilhelm
2006-11-25 13:14         ` Peter Dyballa
2006-11-25 16:32           ` Perry Smith
2006-11-25 18:33             ` Dieter Wilhelm
     [not found]           ` <mailman.1100.1164472360.2155.help-gnu-emacs@gnu.org>
2006-11-25 17:23             ` [OT] " Harald Hanche-Olsen
     [not found]         ` <mailman.1092.1164460454.2155.help-gnu-emacs@gnu.org>
2006-11-25 14:11           ` Harald Hanche-Olsen
2006-11-25 18:27             ` Dieter Wilhelm
     [not found]             ` <mailman.1107.1164479289.2155.help-gnu-emacs@gnu.org>
2006-11-25 19:29               ` Harald Hanche-Olsen
2006-11-25  3:32       ` Perry Smith
2006-11-25 10:11         ` Dieter Wilhelm [this message]
2006-11-25 10:23         ` Peter Dyballa

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=874psn25vp.fsf_-_@hans.local.net \
    --to=dieter@duenenhof-wilhelm.de \
    --cc=Peter_Dyballa@Web.DE \
    --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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.