all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: jidanni@jidanni.org
Cc: 3643@debbugs.gnu.org
Subject: bug#3643: 23.1.90.1; menu, toolbars vs. constant size
Date: Sat, 09 Jan 2010 14:30:41 +0100	[thread overview]
Message-ID: <4B488501.3070002@swipnet.se> (raw)
In-Reply-To: <87skafykq3.fsf@jidanni.org>

jidanni@jidanni.org skrev:
> !.Xresources
> Emacs.toolBar: 0
> Emacs.menuBar: 0
> and emacs -q it turns out work... unless one wants to use a different
> font! Then one needs -mm.
> Is there any way to put the -mm into .emacs? or does one need a shell wrapper?

The documentation for emacs and elisp is in info.  It can be confusing that 
some parts are in the Emacs node and some in the Elisp node.  This particular 
documentation is in the Elisp node: In Emacs:
C-h i m elisp<return> s maximized <return>

I.e. the frame parameter fullscreen can have the value maximized.

> emacs-version "23.1.91.1"
> Anyway, my point still remains, the user's first encounter with
> $ emacs # just won't fit on many people's screens.
> At least under icewm. I don't know any other program that acts like that
> right out of the box.

That is indeed a bad thing to do.  I added some code to address that.  Note 
that any tool bars put there by the window manager must be handeled by the 
window manager.  For example, compiz will never let me create a window so high 
it covers the menu/toolbars added by Gnome-panel.

	Jan D.








      reply	other threads:[~2010-01-09 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 21:41 bug#3643: 23.1.90.1; menu, toolbars vs. constant size jidanni
2010-01-06 11:14 ` Jan Djärv
2010-01-07 10:21   ` jidanni
2010-01-07 11:19     ` Jan Djärv
2010-01-09  4:18       ` jidanni
2010-01-09 13:30         ` Jan Djärv [this message]

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=4B488501.3070002@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=3643@debbugs.gnu.org \
    --cc=jidanni@jidanni.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.