unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>
Cc: 6204@debbugs.gnu.org
Subject: bug#6204: vc-dir always splits the frame
Date: Wed, 26 May 2010 07:26:28 -0700	[thread overview]
Message-ID: <13806D9DC33E4B37A4C0E65AE9ECC628@us.oracle.com> (raw)
In-Reply-To: <4BFCDC43.30702@gmx.at>

>  > The downside to adding such parameters in a case where you 
>  > modify existing functions (esp. if used heavily in
>  > existing code) is that it can make it harder
>  > for 3rd-party code to take advantage of the new feature 
>  > and still work with older versions that do not have the
>  > new parameters.
> 
> I suppose that re-using the `other-window' argument of 
> `display-buffer' as Juri proposed will handle the problem
> you describe.

Dunno. As I say, I haven't really been following this.

As a user and someone who has code that must work with multiple versions, I
would like existing calls to `display-buffer' (and to functions that call it) to
do the same thing across versions.

Any additional behavior that is specific to Emacs 24+ I would like to be able to
choose/determine/set in some other way than via the traditional `display-buffer'
signature.

A global variable is useful for that. The default value of the variable would be
such as to obtain the pre-24 behavior (IOW, that would be the default behavior).

If you instead add optional parameters at the end of the list, that's OK too -
same effect, as long as the default behavior (the behavior for the traditional
signature) is the same as (or very close to) the pre-24 behavior.

That way, someone who makes an ordinary, pre-24-style call to the function gets
the traditional behavior. It is only by making a non-pre-24 call or setting a
new variable to a non-default value that you get the new feature (whatever it
might be).

To me, that is the ideal way to handle this kind of thing. You might have some
specific needs and reasons that conflict with that ideal - dunno. For such a
case *especially*, I would encourage you to take the discussion to the wider dev
forum, emacs-devel. That's what it's for.

HTH.






  reply	other threads:[~2010-05-26 14:26 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17  5:06 bug#6204: vc-dir always splits the frame Glenn Morris
2010-05-17  7:27 ` Dan Nicolaescu
2010-05-19  3:01   ` Glenn Morris
2010-05-19 21:31     ` Juri Linkov
2010-05-20  9:45       ` martin rudalics
2010-05-20 17:14         ` Stefan Monnier
2010-05-20 17:37           ` martin rudalics
2010-05-21 20:15             ` Stefan Monnier
2010-05-22  8:50               ` martin rudalics
2010-05-22 23:51                 ` Juri Linkov
2010-05-23  0:55                   ` Stefan Monnier
2010-05-23  0:59                     ` Juri Linkov
2010-05-23 12:15                       ` martin rudalics
2010-05-23 13:32                         ` Stefan Monnier
2010-05-23 19:04                           ` martin rudalics
2010-05-24 14:07                             ` Stefan Monnier
2010-05-25 15:36                               ` martin rudalics
2010-05-25 17:00                                 ` Stefan Monnier
2010-05-25 17:32                                   ` martin rudalics
2010-05-25 18:01                                     ` Juri Linkov
2010-05-26  8:29                                       ` martin rudalics
2010-05-26 13:54                                         ` Stefan Monnier
2010-05-26 14:49                                           ` martin rudalics
2010-05-27  3:58                                             ` Stefan Monnier
2010-05-25 18:13                                     ` Stefan Monnier
2010-05-26  8:30                                       ` martin rudalics
2010-05-26 13:56                                         ` Stefan Monnier
2010-05-26 14:51                                           ` martin rudalics
2010-05-27  4:04                                             ` Stefan Monnier
2010-05-27  9:09                                               ` martin rudalics
2010-05-27 16:13                                                 ` Stefan Monnier
2010-05-27 17:26                                                   ` martin rudalics
2010-05-27 18:40                                                     ` Stefan Monnier
2010-05-28  9:19                                                       ` martin rudalics
2010-05-28 15:34                                                         ` Stefan Monnier
2010-05-25 18:33                                   ` Drew Adams
2010-05-26  8:30                                     ` martin rudalics
2010-05-26 14:26                                       ` Drew Adams [this message]
2010-05-23 12:15                     ` martin rudalics
2010-05-23 12:14                   ` martin rudalics
2010-05-23  0:52                 ` Stefan Monnier
2010-05-23 12:14                   ` martin rudalics
2010-05-23 13:31                     ` Stefan Monnier
2010-05-21 20:51             ` Juri Linkov
2010-05-22  8:49               ` martin rudalics
2010-05-22 23:54                 ` Juri Linkov
2010-05-22 23:50         ` Juri Linkov
2010-05-23 12:13           ` martin rudalics
2010-05-20 18:33       ` Glenn Morris
2010-05-21  0:16         ` Juri Linkov

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=13806D9DC33E4B37A4C0E65AE9ECC628@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=6204@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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).