unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
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: Thu, 12 Dec 2013 11:15:09 +0100	[thread overview]
Message-ID: <52A98CAD.5020701@gmx.at> (raw)
In-Reply-To: <87sitz3pw3.fsf@mail.jurta.org>

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

 > Do you intend to install this for the next release
 > or it needs more work?

It's merely meant as a proof of concept whether and how persistent
windows work.  It would be a great thing if you (or someone else) filled
in the gory details.  What's needed here is a good feeling for how tabs
are typically used in other applications (I do use tab mix plus on
Firefox but my settings are probably far too exotic) and how to
implement them within the framework of side windows.

 > One problem I noticed immediately:
 > after clicking on the tab it keeps the side window selected.

Yes.  `switch-to-buffer' doesn't seem to be the right answer for this.

BTW, you should set `window-resize-pixelwise' to non-nil in order to
better fit tabs buffers to their contents.  Since I also wrote some code
for window-based tabs I simply attach it here.

martin

[-- Attachment #2: win-tabs.el --]
[-- Type: application/emacs-lisp, Size: 12058 bytes --]

  reply	other threads:[~2013-12-12 10:15 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
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 [this message]
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=52A98CAD.5020701@gmx.at \
    --to=rudalics@gmx.at \
    --cc=16115@debbugs.gnu.org \
    --cc=juri@jurta.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 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).