unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Side Windows
Date: Sat, 24 Sep 2016 22:27:11 +0300	[thread overview]
Message-ID: <83k2e1ayk0.fsf@gnu.org> (raw)
In-Reply-To: <57E6CE9F.603@gmx.at> (message from martin rudalics on Sat, 24 Sep 2016 21:06:07 +0200)

> Date: Sat, 24 Sep 2016 21:06:07 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
> 
>  > A question: would it make sense to invert the meaning of the 'slot'
>  > parameter when the main window shows a buffer whose
>  > bidi-paragraph-direction is right-to-left?  The idea is that when the
>  > main window shows R2L text, the entire geometry of the window
>  > arrangement should switch direction, at least optionally, otherwise
>  > applications that want that will have to include tedious code to
>  > recompute the slots on the fly.
> 
> Suppose the main window shows a left-to-right buffer and we have two
> bottom side windows.  Switching to a right-to-left buffer in the main
> window would now mean to exchange the buffers shown in the side windows.
> We would also have to renumber these windows, resize them maybe,
> exchange their parameters and some of those properties stored in window
> configurations.  And we would have to adjust all overlays with a
> `window' property in those windows.  It's certainly possible to do all
> that but it's not entirely trivial.

What's the alternative? that the application programmer does all that
in their application code?  What are the chances of them getting this
right?

> Personally, I think that such layout decisions should be made before the
> first side window is created.

That might be impossible in the general case, because the same window
arrangement could be used for displaying buffers of different
directions.  One example is an email client that shows messages in the
main window.

> I doubt that you change the menubar layout whenever you switch
> `bidi-paragraph-direction'.

Some applications out there actually do that.  Emacs doesn't, but only
because I deliberately decided it wasn't TRT (there's a FIXME comment
about that in the sources).  Menu bars are different, because they are
not really associated with any particular window, they are associated
with a frame.

> But in practice I never work with bidirectional text so I can't
> really tell.

I think we should at least allow for such a behavior as an option.

Thanks.



  reply	other threads:[~2016-09-24 19:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  9:07 Side Windows martin rudalics
2016-09-22 20:54 ` Juri Linkov
2016-09-24 19:05   ` martin rudalics
2016-09-23  8:38 ` Eli Zaretskii
2016-09-23  9:14   ` Eli Zaretskii
2016-09-24 19:06   ` martin rudalics
2016-09-24 19:27     ` Eli Zaretskii [this message]
2016-10-05  8:39       ` martin rudalics
2016-10-05 10:35         ` Eli Zaretskii
2016-10-05 13:13         ` Eli Zaretskii
2016-10-05 14:20           ` martin rudalics
  -- strict thread matches above, loose matches on Subject: below --
2016-10-05 10:26 Angelo Graziosi
2016-10-05 10:51 ` Eli Zaretskii
2016-10-05 11:01   ` Angelo Graziosi
2016-10-05 11:24     ` Kaushal Modi
2016-10-05 13:03     ` Eli Zaretskii
2016-10-05 10:25 Angelo Graziosi
2010-04-13 19:53 Gtk tabs in emacs, new branch grischka
2010-04-13 23:31 ` Side windows (was: Gtk tabs in emacs, new branch.) Juri Linkov
2010-04-14  3:18   ` Eli Zaretskii
2010-04-14 15:24     ` Side windows Jason Rumney
2010-04-14 16:52       ` Juri Linkov
2010-04-14 18:19         ` Eli Zaretskii
2010-04-14 23:54           ` Juri Linkov
2010-04-15  3:18             ` Eli Zaretskii
2010-04-15 23:46               ` Juri Linkov
2010-04-16  6:33                 ` Eli Zaretskii
2010-04-14  5:15   ` Jan Djärv
2010-04-16 14:03   ` grischka
2010-04-16 20:48     ` 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=83k2e1ayk0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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).