unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bozhidar Batsov <bozhidar.batsov@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Condider adding buffer-mode
Date: Thu, 31 Oct 2013 14:57:25 +0200	[thread overview]
Message-ID: <CAM9Zgm205a8F5TbwynKkz7k8mKnA-gDV=3XqBP8m8A+n5iFSsw@mail.gmail.com> (raw)
In-Reply-To: <jwvwqkvue9a.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

On 30 October 2013 14:41, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> > current buffer). While this is OK for interactive code, it seems pretty
> > obnoxious when done in library code. We can very well have a version of
> > `derived-mode-p' that operates on an explicit buffer argument as opposed
> to
> > an implicit one.
>
> But this applies to many other things.  IOW you're complaining about
> Emacs's design.
>

Fair enough.


>
> > I know that Emacs Lisp places little value on functional programming
> > principles, but I don't see the harm in embracing them at
> > least occasionally.
>
> Just adding something like buffer-mode is not going to help enough to
> justify adding a function.  You're trying to work against the tool.
>
>
>         Stefan
>

OK. Consider the matter closed then.


-- 
Best Regards,
Bozhidar Batsov

http://www.batsov.com

[-- Attachment #2: Type: text/html, Size: 1773 bytes --]

      reply	other threads:[~2013-10-31 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 14:22 Condider adding buffer-mode Bozhidar Batsov
2013-10-24 21:46 ` Stefan Monnier
2013-10-29 15:53   ` Bozhidar Batsov
2013-10-29 16:36     ` Stefan Monnier
2013-10-29 17:28       ` Bozhidar Batsov
2013-10-29 21:56         ` Stefan Monnier
2013-10-30  9:34           ` Bozhidar Batsov
2013-10-30 12:41             ` Stefan Monnier
2013-10-31 12:57               ` Bozhidar Batsov [this message]

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='CAM9Zgm205a8F5TbwynKkz7k8mKnA-gDV=3XqBP8m8A+n5iFSsw@mail.gmail.com' \
    --to=bozhidar.batsov@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

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

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).