From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: enriched-mode and switching major modes. Date: Thu, 23 Sep 2004 09:13:27 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <200409042358.i84Nwjt19152@raven.dms.auburn.edu> <87llfn5ihw.fsf@emacswiki.org> <01c49c75$Blat.v2.2.2$7a37cb00@zahav.net.il> <01c49d70$Blat.v2.2.2$f7cfb860@zahav.net.il> <01c49da7$Blat.v2.2.2$cd5f7160@zahav.net.il> <01c4a0d0$Blat.v2.2.2$37047fe0@zahav.net.il> <01c4a128$Blat.v2.2.2$85118c20@zahav.net.il> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1095923656 21305 80.91.229.6 (23 Sep 2004 07:14:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 23 Sep 2004 07:14:16 +0000 (UTC) Cc: epameinondas@gmx.de, boris@gnu.org, emacs-devel@gnu.org, alex@emacswiki.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 23 09:13:58 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CANni-0003sB-00 for ; Thu, 23 Sep 2004 09:13:58 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CANti-0003kZ-L9 for ged-emacs-devel@m.gmane.org; Thu, 23 Sep 2004 03:20:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CANtX-0003kS-Rj for emacs-devel@gnu.org; Thu, 23 Sep 2004 03:19:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CANtW-0003kG-At for emacs-devel@gnu.org; Thu, 23 Sep 2004 03:19:59 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CANtW-0003kD-7Z for emacs-devel@gnu.org; Thu, 23 Sep 2004 03:19:58 -0400 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1CANnE-00011f-Mh for emacs-devel@gnu.org; Thu, 23 Sep 2004 03:13:29 -0400 Original-Received: (qmail 25191 invoked from network); 23 Sep 2004 07:13:27 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 23 Sep 2004 07:13:27 -0000 Original-To: Eli Zaretskii In-Reply-To: <01c4a128$Blat.v2.2.2$85118c20@zahav.net.il> (Eli Zaretskii's message of "Thu, 23 Sep 2004 06:47:05 +0200") User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:27475 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:27475 "Eli Zaretskii" writes: >> Cc: epameinondas@gmx.de, boris@gnu.org, alex@emacswiki.org, >> emacs-devel@gnu.org >> From: storm@cua.dk (Kim F. Storm) >> Date: Wed, 22 Sep 2004 23:53:29 +0200 >> >> We could add before-beginning-of-buffer-hook and >> after-end-of-buffer-hook which are hooks which are run when point is >> moved backwards when (bolp) or forwards at (eobp). These could be >> setup to jump to the proper position in the "parent window". > > What about "C-a" and "C-e"? shouldn't they go to the left and right > margin of the surrounding parent window? Perhaps -- it depends on how things a layed out. E.g if I have text and image (IIII) like this: abc IIII defgh IIII jkl IIII and cursor is on `f' I would probably prefer if C-e moved cursor to the position after the 'h' rather than to the right edge of the IIIImage. > > What about "C-x o"? it will allow jumping into what the user thinks is > a part of the current window, which is confusing. C-x o (and C-x 4 f etc) should ignore anonymous windows. I think most of the relevant commands use a small number of functions to select the target window -- we only need to fix those functions, not each command. > > I can see many similar complications. Sure, it need to be thought about before implementing anything. In a block model used for WP, there are probably lots of similar problems that we would have to solve. I don't think that can be avoided no matter which approach we choose. -- Kim F. Storm http://www.cua.dk