all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Leo Liu <sdl.web@gmail.com>,
	"18643@debbugs.gnu.org" <18643@debbugs.gnu.org>
Subject: bug#18643: 25.0.50; elisp--expect-function-p
Date: Sat, 11 Oct 2014 20:18:34 +0400	[thread overview]
Message-ID: <5439585A.3030201@yandex.ru> (raw)
In-Reply-To: <jwv1tqe7m8b.fsf-monnier+emacsbugs@gnu.org>

On 10/11/2014 05:47 PM, Stefan Monnier wrote:

> But by being a separate function, users can add/remove it at will,
> depending on their preference.

Hmm, that's one option, yes.

>> I rather think the right solution would start with a stricter convention for
>> code snippets in docstrings.
>
> That's a non-starter, because while we can apply this to our own code,
> we can't enforce it on others's,

Then those others won't get Lisp completion is docstrings. Which is 
their choice, and not that big a deal.

The convention doesn't have to be complicated. For example, we can limit 
ourselves to considering blocks within comments or docstrings separated 
by newlines from the rest of the text, and only when each line starts 
with 2+ (or 4+?) spaces. As a plus, we'll be able to modify the 
indentation function to work in these blocks, too.





  reply	other threads:[~2014-10-11 16:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06  5:13 bug#18643: 25.0.50; elisp--expect-function-p Leo Liu
2014-10-09  2:50 ` Dmitry Gutov
2014-10-09  3:31   ` Leo Liu
2014-10-09  6:17     ` Dmitry Gutov
2014-10-09 15:27     ` Stefan Monnier
2014-10-09 23:43       ` Leo Liu
2014-10-10  1:16         ` Stefan Monnier
2014-10-10  4:07           ` Leo Liu
2014-10-10 13:25             ` Stefan Monnier
2014-10-10 20:53               ` Dmitry Gutov
2014-10-11  0:25                 ` Leo Liu
2014-10-11 13:48                   ` Stefan Monnier
2014-10-11 14:21                     ` Leo Liu
2014-10-14 18:32                       ` Stefan Monnier
2014-10-16  2:42                         ` Dmitry Gutov
2014-10-16 13:10                           ` Stefan Monnier
2014-10-11 13:47                 ` Stefan Monnier
2014-10-11 16:18                   ` Dmitry Gutov [this message]
2014-10-14 18:34                     ` Stefan Monnier
2014-10-16  2:35                       ` Dmitry Gutov
2014-10-16  3:36                         ` Leo Liu
2014-10-16  9:59                           ` Dmitry Gutov
2014-10-11  0:16               ` Leo Liu
2014-10-10  3:56         ` Dmitry Gutov
2014-10-10  4:33           ` Leo Liu
2014-10-11 16:31             ` Dmitry Gutov
2014-10-10  3:34       ` Dmitry Gutov
2014-10-10 13:20         ` Stefan Monnier
2014-10-11 17:07           ` Dmitry Gutov
2022-04-26 13:44 ` Lars Ingebrigtsen
2022-04-26 15:46   ` Leo Liu
2022-04-27 11:52     ` Lars Ingebrigtsen

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=5439585A.3030201@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=18643@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sdl.web@gmail.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 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.