From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: xdisp.c's struct it questions. Date: Sun, 4 Oct 2015 13:44:31 +0000 Message-ID: <20151004134431.GA22632@acm.fritz.box> References: <20151003154835.GA4509@acm.fritz.box> <83r3lc2au2.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1443966216 7796 80.91.229.3 (4 Oct 2015 13:43:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 Oct 2015 13:43:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 04 15:43:25 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZijZT-0006n0-Kn for ged-emacs-devel@m.gmane.org; Sun, 04 Oct 2015 15:43:23 +0200 Original-Received: from localhost ([::1]:42481 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZijZQ-0005FZ-Ci for ged-emacs-devel@m.gmane.org; Sun, 04 Oct 2015 09:43:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48153) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZijZD-0005FN-TT for emacs-devel@gnu.org; Sun, 04 Oct 2015 09:43:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZijZA-0005z5-NJ for emacs-devel@gnu.org; Sun, 04 Oct 2015 09:43:07 -0400 Original-Received: from mail.muc.de ([193.149.48.3]:62313) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZijZA-0005yt-Di for emacs-devel@gnu.org; Sun, 04 Oct 2015 09:43:04 -0400 Original-Received: (qmail 8319 invoked by uid 3782); 4 Oct 2015 13:43:02 -0000 Original-Received: from acm.muc.de (p548A414F.dip0.t-ipconnect.de [84.138.65.79]) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 04 Oct 2015 15:43:02 +0200 Original-Received: (qmail 22675 invoked by uid 1000); 4 Oct 2015 13:44:31 -0000 Content-Disposition: inline In-Reply-To: <83r3lc2au2.fsf@gnu.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Delivery-Agent: TMDA/1.1.12 (Macallan) X-Primary-Address: acm@muc.de X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x X-Received-From: 193.149.48.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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 Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:190879 Archived-At: Hello again, Eli. On Sat, Oct 03, 2015 at 07:09:09PM +0300, Eli Zaretskii wrote: > > Date: Sat, 3 Oct 2015 15:48:36 +0000 > > From: Alan Mackenzie > > I'm trying to get some stuff in xdisp.c working. It's hard. > My sympathies. Please consider recording in the comments everything > you learn that isn't already there. Let's take something positive and > useful from your ordeal ;-) The biggest time sink for me at the moment is the vagueness in xdisp.c's use of the word "line". Sometimes it means a screen line, sometimes it means a text line. An example is `forward_to_next_line_start'. It sounds like just what I need, but is it? If it were called `forward_to_next_screen_line_start', or `forward_to_next_text_line_start', I could save myself an awful lot of poring through source code. Even the comments preceding these routines tend to be vague about this. A positive example is `move_it_in_display_line_to', which is explicit about what sort of line it means. -- Alan Mackenzie (Nuremberg, Germany).