From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: trunk r113878: Refine previous change. Date: Thu, 15 Aug 2013 12:42:43 -0400 Message-ID: References: <834nasoy4d.fsf@gnu.org> <87txirc596.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1376584990 22243 80.91.229.3 (15 Aug 2013 16:43:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 15 Aug 2013 16:43:10 +0000 (UTC) Cc: xfq.free@gmail.com, Juanma Barranquero , Eli Zaretskii , Emacs developers To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 15 18:43:10 2013 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 1VA0di-0000pi-FZ for ged-emacs-devel@m.gmane.org; Thu, 15 Aug 2013 18:43:10 +0200 Original-Received: from localhost ([::1]:54448 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VA0di-0007a0-3s for ged-emacs-devel@m.gmane.org; Thu, 15 Aug 2013 12:43:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54502) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VA0dY-0007VS-Ip for emacs-devel@gnu.org; Thu, 15 Aug 2013 12:43:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VA0dQ-000118-P6 for emacs-devel@gnu.org; Thu, 15 Aug 2013 12:43:00 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:26602) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VA0dI-0000zI-Q7; Thu, 15 Aug 2013 12:42:44 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFLd/Nq/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDpHqBXoMT X-IPAS-Result: Av4EABK/CFFLd/Nq/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDpHqBXoMT X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="21951426" Original-Received: from 75-119-243-106.dsl.teksavvy.com (HELO pastel.home) ([75.119.243.106]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 15 Aug 2013 12:42:37 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 7539066215; Thu, 15 Aug 2013 12:42:43 -0400 (EDT) In-Reply-To: <87txirc596.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 15 Aug 2013 12:01:41 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:162777 Archived-At: >> FWIW, I've fairly often written code which uses goto-char with >> a position that can be outside of point-min...point-max, knowing that it >> will go to the closest possible position. > Did you ever pass a negative position? > Were you passing a position outside the currently accessible portion of > the buffer, but within the unnarrowed limits, or was it just an arbitrarily > large value to mean "point-max" (and if so, why not just use point-max)? Typically it's a slightly sloppy value. E.g. (1- pos) or (1+ pos) or just `pos' but where that position was valid in the past and some buffer changes may have rendered it invalid. So it typically is a valid position in 99% of the cases, but I know that it's not guaranteed to be so in 100% of the cases. Stefan