From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.help Subject: RE: Bookmark the end of file? Date: Sun, 12 Apr 2015 13:42:38 -0700 (PDT) Message-ID: <1b751175-4544-44e7-bbcd-d5a01bf92624@default> References: <87vbh8hlns.fsf@wmi.amu.edu.pl> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1428871411 24316 80.91.229.3 (12 Apr 2015 20:43:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Apr 2015 20:43:31 +0000 (UTC) To: Stefan Monnier , help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Apr 12 22:43:18 2015 Return-path: Envelope-to: geh-help-gnu-emacs@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 1YhOir-0007iY-In for geh-help-gnu-emacs@m.gmane.org; Sun, 12 Apr 2015 22:43:17 +0200 Original-Received: from localhost ([::1]:46231 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhOiq-0008EY-JF for geh-help-gnu-emacs@m.gmane.org; Sun, 12 Apr 2015 16:43:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35216) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhOih-0008ET-66 for help-gnu-emacs@gnu.org; Sun, 12 Apr 2015 16:43:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YhOid-0002ny-UV for help-gnu-emacs@gnu.org; Sun, 12 Apr 2015 16:43:07 -0400 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:38614) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YhOid-0002no-OH for help-gnu-emacs@gnu.org; Sun, 12 Apr 2015 16:43:03 -0400 Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t3CKh2Tu020022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 12 Apr 2015 20:43:02 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id t3CKh1j1027200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 12 Apr 2015 20:43:01 GMT Original-Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by userv0122.oracle.com (8.13.8/8.13.8) with ESMTP id t3CKh1VF008492; Sun, 12 Apr 2015 20:43:01 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: userv0021.oracle.com [156.151.31.71] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 141.146.126.69 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:103665 Archived-At: > > > I think it'd be OK to refine the current code such that a bookmark > > > that's at a position equal to point-max would be marked as "go the EO= B" > > > instead of "go to the position that happened to be EOB back when we > > > created the bookmark". > > > > Unless that's not what the user wants. ;-) > > Do you assume that most users want to track eob in such a case? ... > > Consider also this comment for the code that automatically > > relocates a bookmark when you jump to it, to keep it within/near > > its originally recorded context: > > > > ;; ... it's better to be put before it so you can read it, > > ;; rather than after and remain perhaps unaware of the changes. >=20 > The EOB is an extremely important part of the context. So, yes, if > point was at EOB when you set the bookmark, I think the user will > more often be satisfied if we store "EOB" rather than if we store > "the position that was EOB when the bookmark was set". Unless that's not what the user wants. ;-) As I said,=20 > > there are different use cases to consider. One approach is to > > offer users some ways to obtain one or the other behavior after the > > (ordinary) bookmark has been created.... Another approach could be > > to let users choose the behavior when a bookmark is created at eob Even if you were right that one use case is more common, why wouldn't we want to let users control the behavior, instead of deciding it for them at coding time? IOW, instead of guessing what will make users "more often be satisified", why not let them decide what satisfies them in any given context?