all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Aliaksey Kandratsenka <alkondratenko@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to make "C-x 4" command work better for widescreen monitor
Date: Wed, 29 Oct 2008 00:28:46 -0700 (PDT)	[thread overview]
Message-ID: <8d3e0239-7eeb-403d-932f-c7d091c8ab35@m32g2000hsf.googlegroups.com> (raw)
In-Reply-To: 8a26fb47-c638-4d77-a493-61826a959d8e@b31g2000prb.googlegroups.com

On Oct 28, 8:59 pm, Pony <lingyu.ma...@googlemail.com> wrote:
> When we run the command "C-x 4 f", which will open a new file in a new
> buffer under the current one,
> the Emacs will cut the whole window into two vertical ones, each takes
> 50% space of the screen.
>
> However at present more and more people begin to use widescreen tft
> monitor for programming,
> in my opinion it will be much better that, after we run "C-x 4"
> commands the Emacs cut the whole screen into two HORIZONTALL screens.

Hi. Sorry for not answering your original question, but I'd like to
express my opinion on widescreen monitors for development.
I think that for typical code with few long lines it makes more sense
to use 'tallscreen' monitors than widescreen. That way more useful
information will fit into screen.

At home I have usual monitor which can be rotated to portrait mode. I
have used portrait mode (with corresponding image rotation via xrandr,
of course) several times for programming and this seems like good
option.

Aliaksey


  parent reply	other threads:[~2008-10-29  7:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 18:59 How to make "C-x 4" command work better for widescreen monitor Pony
2008-10-28 22:37 ` Xah
2008-10-29  7:28 ` Aliaksey Kandratsenka [this message]
2008-10-29 15:49 ` Giorgos Keramidas
2008-10-29 17:32 ` Rupert Swarbrick

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8d3e0239-7eeb-403d-932f-c7d091c8ab35@m32g2000hsf.googlegroups.com \
    --to=alkondratenko@gmail.com \
    --cc=help-gnu-emacs@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.