From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: dired-duplicates Date: Thu, 09 Nov 2023 10:48:42 +0200 Message-ID: <83y1f7z505.fsf@gnu.org> References: <83edha9mlg.fsf@gnu.org> <87h6m5shpf.fsf@gmail.com> <831qd9a7gg.fsf@gnu.org> <87lebhz78r.fsf@posteo.net> <83sf5p8efg.fsf@gnu.org> <2b30b6e0-d30e-41e1-83a5-05b0c3fa8aa6@gmx.at> <83lebg8zsu.fsf@gnu.org> <715392ae-8ae8-449e-905b-8ff2aa6a2e5a@gmx.at> <837cmr1nja.fsf@gnu.org> <48fece87-5bd9-4d37-a6bb-2e9b9da00bc2@gmx.at> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29545"; mail-complaints-to="usenet@ciao.gmane.io" Cc: h.judt@gmx.at, emacs-devel@gnu.org To: tomas@tuxteam.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Nov 09 09:49:17 2023 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 1r10iz-0007RO-RX for ged-emacs-devel@m.gmane-mx.org; Thu, 09 Nov 2023 09:49:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r10il-00058v-UI; Thu, 09 Nov 2023 03:49:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r10ih-00058Q-Rd for emacs-devel@gnu.org; Thu, 09 Nov 2023 03:49:00 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r10ih-0004oE-H6; Thu, 09 Nov 2023 03:48:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=vzh4tAyR/qD+1aQ7nuGyKY0/WhTbIlS33KtI6BYmpjQ=; b=N0VuNVZEzDuq v/AAC59kApe7PDFY+TzrZIWu/pqcQfoKa92jwB9JN5B/tCXidKwhQKNgQYTdOtcc1iWbRHucTOfzc qlEYfHsG2eXtAVDyJJa3vEgbevAgqzfnUlVpGdI6iiVz58PvUvXI7dI121fWgP5ucetsUTKVzXHCq WrjhjTiaJjW9NVK6OefRASO+B18mmiCjqdsv9HuQGlgeFLYPLsMsLSsocQzsxs/JfpN5Jv4w5PeQI eaT2fzXb5OcMKQvBoskEgAHSmfYYkPMrCr47Bk///IOn+CMN/vD6BXk57IjWc+l47qog9CwWxqU9W AO+0cOy9Uf096qTwUgvngg==; In-Reply-To: (tomas@tuxteam.de) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:312389 Archived-At: > Date: Thu, 9 Nov 2023 09:38:50 +0100 > Cc: Eli Zaretskii , emacs-devel@gnu.org > From: > > On Thu, Nov 09, 2023 at 09:00:11AM +0100, Harald Judt wrote: > > [...] > > > Yes, but I wonder, why do this? There can be 32-bit systems as well as > > 64-bit systems that can have only 2GiB RAM, both might fail when trying to > > open a file that has e.g. 1536MiB. Then, there might be both types of > > systems that have 8gb of RAM that can open such files with no problems? > > Eli's remark was about Emacs's integer size (which is used to address > spots in buffers). On 32 bit *builds* it isn't wide enough for big > buffers. On 64 bit builds it is. > > It's about Emacs's build, not the OS around it. Think "address space", > just one or two onion layers further. Actually, it's about both.