unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: "João Távora" <joaotavora@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Visual bell patch for emacs on OSX
Date: Wed, 25 Dec 2013 17:30:33 +0100	[thread overview]
Message-ID: <51E2AD4E-1A33-40E5-96AA-D5E62471D4C9@swipnet.se> (raw)
In-Reply-To: <CALDnm51-0V=sWLZWCaoM0Yt32N+HODdC0Xp0xDCirmexLMvNcw@mail.gmail.com>

Hi.

24 dec 2013 kl. 10:56 skrev João Távora <joaotavora@gmail.com>:

> On Mon, Dec 23, 2013 at 12:09 PM, Jan Djärv <jan.h.d@swipnet.se> wrote:
>> I checked in a fix in trunk, please try again.
>> 
> Thanks.
> 
> So I did that and GNUstep emacs compiled OK.
> 
> Starting it brings up some kind of top-level menu, a ying-yang-
> something square, and emacs itself. I see all my config getting
> loaded, the only difference to the GTK case being that it's a little
> slower and some fonts look different.
> 

GNUStep has a general problem with fonts, I have yet to discover how to configure this correctly, if even possible.

> However the big difference is that I can't place the mouse on the
> application or give emacs any input. This is apparently some kind of
> window-manager issue. Can a gnustep-enabled app be used on top of
> normal window managers like fluxbox and stumpwm? If not, what window
> manager, if any, should I be using?

It works fine here with normal window managers (Gnome 3 and Unity).  The GNUStep window manager is WindowMaker.

> 
> Though admittedly I didn't dig a lot, I don't seem to find an answer
> to this in
> 
>   http://www.gnustep.org/information/aboutGNUstep.html
> 
> I understand that gnustep is not a window manager and runs on top of
> X11, but then how to manage windows, specifically, how to make input
> reach them?

Click on them?  That is what I do.

	Jan D.





  reply	other threads:[~2013-12-25 16:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 22:45 Visual bell patch for emacs on OSX João Távora
2013-12-16 23:05 ` Glenn Morris
2013-12-16 23:46   ` Glenn Morris
2013-12-16 23:49   ` João Távora
2013-12-17  0:14     ` Glenn Morris
2013-12-17  2:11     ` Stefan Monnier
2013-12-17 16:59       ` Jan Djärv
2013-12-18 12:52         ` Bozhidar Batsov
2013-12-18 14:21           ` Stefan Monnier
2013-12-18 14:52             ` Bozhidar Batsov
2013-12-18 15:16               ` Jan Djärv
2013-12-21  0:11         ` João Távora
2013-12-21  8:19           ` Jan Djärv
2013-12-23 12:09             ` Jan Djärv
2013-12-24  9:56               ` João Távora
2013-12-25 16:30                 ` Jan Djärv [this message]
2013-12-21  8:56           ` martin rudalics
  -- strict thread matches above, loose matches on Subject: below --
2013-12-17  8:35 François-Xavier Bois
2013-12-17 15:11 ` Jan Djärv

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=51E2AD4E-1A33-40E5-96AA-D5E62471D4C9@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).