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: 16115@debbugs.gnu.org
Subject: bug#16115: 24.3.50; doc string of `display-buffer-in-side-window' - there is no SIDE arg
Date: Wed, 11 Dec 2013 10:57:40 -0800 (PST)	[thread overview]
Message-ID: <dab745b1-4a5c-4d0e-9b3b-6cb93607b6b9@default> (raw)
In-Reply-To: <52A8A708.9070801@gmx.at>

>  > Subject line says it all.  The doc string speaks of SIDE, as if there
>  > were a SIDE argument.  There is none.
> 
> Thanks.  Should be fixed now.

That was quick.  Thanks.

> I couldn't resist to attach a file where you can see how this function
> can be used.

Looks interesting.  When I loaded it I got this message:
Wrong type argument: listp, :inherit

This is one offender:
(defface frame-tabs-higlight-tab
  '((t :inherit frame-tabs-item-tab
       :foreground "white"
       :background "green3"))
  "Face for highlighting frame tabs item."
  :version "24.4"
  :group 'frame-tabs)

But if I try `C-M-x' on that twice, the first time gives the error and
the second defines it OK.  Likewise for the other face defs.

Haven't tried to dig into it further - no time now.

(BTW, spelling typos: "higlight" -> "highlight".)

Wrt the function (and how I discovered its doc), I just used it in an
answer to a StackOverflow question.  Dunno whether my answer is
appropriate or a good use of the function.  Probably there is a simpler
and better answer.

http://stackoverflow.com/a/20525430/729907





  reply	other threads:[~2013-12-11 18:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 16:59 bug#16115: 24.3.50; doc string of `display-buffer-in-side-window' - there is no SIDE arg Drew Adams
2013-12-11 17:55 ` martin rudalics
2013-12-11 18:57   ` Drew Adams [this message]
2013-12-11 19:01     ` Drew Adams
2013-12-12 10:14     ` martin rudalics
2013-12-12 16:18       ` Drew Adams
2013-12-12 18:09         ` martin rudalics
2013-12-12 19:50           ` Drew Adams
2013-12-14 11:22             ` martin rudalics
2013-12-13 21:54           ` Juri Linkov
2013-12-14 11:23             ` martin rudalics
2013-12-14 16:20               ` Drew Adams
2013-12-14 17:17                 ` martin rudalics
2013-12-14 17:16             ` martin rudalics
2013-12-15 19:56               ` Juri Linkov
2013-12-16 10:10                 ` martin rudalics
2013-12-16 20:19                   ` Juri Linkov
2013-12-17 17:31                     ` martin rudalics
2013-12-11 23:54   ` Juri Linkov
2013-12-12 10:15     ` martin rudalics
2013-12-12 18:25       ` Stefan Monnier
2013-12-13 10:13         ` martin rudalics
2013-12-13 10:56           ` Eli Zaretskii
2013-12-14 11:23             ` martin rudalics
2013-12-14 12:09               ` Eli Zaretskii
2013-12-14 13:45                 ` martin rudalics
2013-12-14 14:06                   ` Eli Zaretskii
2013-12-13  1:18       ` Juri Linkov
2013-12-13 10:13         ` martin rudalics

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=dab745b1-4a5c-4d0e-9b3b-6cb93607b6b9@default \
    --to=drew.adams@oracle.com \
    --cc=16115@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).