unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alin Soare <as1789@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: martin rudalics <rudalics@gmx.at>, Emacs Dev <emacs-devel@gnu.org>
Subject: Re: Tabs are ready?
Date: Thu, 2 Feb 2012 23:44:24 +0200	[thread overview]
Message-ID: <CA+Xtq3Wpze107bHwn3yBFaNf6qFvm05zjHEcNoNGv79Kb4hvXQ@mail.gmail.com> (raw)
In-Reply-To: <87ehudorq8.fsf@mail.jurta.org>

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

> > Whatever implementation will be , it must define the events as elisp
> > functions ; even after the creation of a tab, there must be an event that
> > calls a lisp function.
>
> In http://bzr.sv.gnu.org/lh/emacs/x-tabs I added a new frame parameter
> `tab_bar_lines' that holds a keymap with items bound to Lisp functions.
>
>
I did the same.



> But now I tend to try side windows and atomic windows because
> frame-level features (like a frame parameter or native GTK tabs)
> are of no help for implementing per-window tabs.
>

That is also a possibility, but they must respond to events, too.

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

  reply	other threads:[~2012-02-02 21:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 22:18 Tabs are ready? Alin Soare
2012-02-02  1:15 ` Juri Linkov
2012-02-02 11:08   ` martin rudalics
2012-02-02 11:54     ` Alin Soare
2012-02-02 13:18       ` martin rudalics
2012-02-02 13:21         ` Alin Soare
2012-02-02 21:22       ` Juri Linkov
2012-02-02 21:44         ` Alin Soare [this message]
2012-02-02 21:17     ` Juri Linkov
2012-02-03 18:24       ` martin rudalics
2012-02-03 20:27         ` Juanma Barranquero
2012-02-04 13:56           ` martin rudalics
2012-02-02 21:41   ` Alin Soare

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=CA+Xtq3Wpze107bHwn3yBFaNf6qFvm05zjHEcNoNGv79Kb4hvXQ@mail.gmail.com \
    --to=as1789@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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).