From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: [PATCH] When deleting in bookmark menu, prompt for confirmation. Date: Sat, 08 May 2021 01:13:00 -0500 Message-ID: <87lf8p3g9f.fsf@red-bean.com> References: <87a6pcqy7s.fsf@red-bean.com> <83czu86o46.fsf@gnu.org> <835z006jpl.fsf@gnu.org> <87im3z3f8f.fsf@red-bean.com> <83zgxb67g2.fsf@gnu.org> <87mtt9sqh4.fsf@red-bean.com> <87czu58uso.fsf@gnus.org> <878s4tq8e6.fsf@red-bean.com> <874kfguail.fsf@red-bean.com> <875yzwtkuj.fsf@gmail.com> <875yzu5tkq.fsf@red-bean.com> Reply-To: Karl Fogel Mime-Version: 1.0 Content-Type: text/plain; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27172"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Lars Ingebrigtsen , Matthias Meulien , Stefan Monnier , "emacs-devel@gnu.org" To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 08 08:14:37 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lfGEX-0006y6-AQ for ged-emacs-devel@m.gmane-mx.org; Sat, 08 May 2021 08:14:37 +0200 Original-Received: from localhost ([::1]:38252 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lfGEW-0003jV-AQ for ged-emacs-devel@m.gmane-mx.org; Sat, 08 May 2021 02:14:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52422) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lfGD6-0002Lp-3T for emacs-devel@gnu.org; Sat, 08 May 2021 02:13:08 -0400 Original-Received: from sanpietro.red-bean.com ([45.79.25.59]:39488) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lfGD4-0002un-1u for emacs-devel@gnu.org; Sat, 08 May 2021 02:13:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=red-bean.com; s=202005newsp; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:Reply-To:References:Subject:Cc:To:From:Sender: Content-Transfer-Encoding:Content-ID:Content-Description; bh=Ad2WmQRa5V1RAyZB9JTBW1NNDYzcB3u8+AhBX2c8P8E=; t=1620454385; x=1621663985; b=jvjms8AdbePyr0hRIR5aRU5l1x7zhvd2BGeeLc0w2lwN8TDO+hhaw344TdVWGb8cHsHxiy2G66 CykTQn1llfGG2n2rwU3aHtb6YKyxqJnkxPGfBQQLesZEU0QYrfbOiYX7zQo52L3RYwRPqkuTIrU1M ACNAav/LzLgVx6OJt3Hx1lZ41EpNbAWTKhUypuqMbwvt4OJKeOPIzM+YzX3cbKZ/T6fMTQLXQPefW CXxBF2nrps2hTxExBTH7XQH7gPa6z9xEOYzCma1J26CjDm9PRFbAtB0OzTZM4jtKH8qWqSJGdjOCw OIodRsu5n5BNU+uuWUDLZjaTHlL/cd0IRfw3g==; Original-Received: from 99-112-125-163.lightspeed.cicril.sbcglobal.net ([99.112.125.163]:40356 helo=floss) by sanpietro.red-bean.com with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lfGD1-0008SC-Ex; Sat, 08 May 2021 06:13:03 +0000 In-Reply-To: (Drew Adams's message of "Fri, 7 May 2021 22:24:28 +0000") Received-SPF: pass client-ip=45.79.25.59; envelope-from=kfogel@red-bean.com; helo=sanpietro.red-bean.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:269017 Archived-At: On 07 May 2021, Drew Adams wrote: >> However, since we don't get many bug reports about it in >> practice, I'm not sure it's worth solving. If anything, it >> might >> be an argument for removing the multiple-bookmark-files >> functionality and just admitting that everyone's just using the >> one default file :-). > >That would really be too bad. Don't worry, I'm not sure enough about these hypothetical usage patterns to actually make the change. Whatever people are doing, it's not resulting in bug reports here, so I wouldn't go looking for trouble! Best regards, -Karl >Dunno whether that would mean that Bookmark+ would >need to incorporate the pre-change vanilla code. >Maybe the Bookmark+ code already side-steps the >vanilla code sufficiently in this regard to not >be bitten by such an (unfortunate) change. > >There really is no good reason not to allow >multiple bookmarks with the same name...