From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bozhidar Batsov Newsgroups: gmane.emacs.devel Subject: Re: Default history-length should be higher Date: Sun, 26 Jan 2014 21:22:37 +0200 Message-ID: References: <7a6753c5-cac9-4e60-be73-42467784e8eb@default> <8761p7uykd.fsf@maru2.md5i.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c329a296eaa104f0e483fa X-Trace: ger.gmane.org 1390764173 7078 80.91.229.3 (26 Jan 2014 19:22:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 26 Jan 2014 19:22:53 +0000 (UTC) Cc: emacs-devel To: Michael Welsh Duggan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 26 20:23:01 2014 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 1W7VIJ-0002So-OC for ged-emacs-devel@m.gmane.org; Sun, 26 Jan 2014 20:22:59 +0100 Original-Received: from localhost ([::1]:55963 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7VIJ-0001lP-B2 for ged-emacs-devel@m.gmane.org; Sun, 26 Jan 2014 14:22:59 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47576) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7VI5-0001VH-0V for emacs-devel@gnu.org; Sun, 26 Jan 2014 14:22:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W7VHz-000802-Om for emacs-devel@gnu.org; Sun, 26 Jan 2014 14:22:44 -0500 Original-Received: from mail-ob0-x22f.google.com ([2607:f8b0:4003:c01::22f]:48159) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7VHz-0007zn-HG for emacs-devel@gnu.org; Sun, 26 Jan 2014 14:22:39 -0500 Original-Received: by mail-ob0-f175.google.com with SMTP id wn1so5578686obc.20 for ; Sun, 26 Jan 2014 11:22:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=kV3a15NjKCy+WmumexdaQu44zJ/ua2JN4+kVWGX2v6A=; b=i6yHUwNTFS8r18MJ0PKHt5VHHO5jsCCzjD27cKi1BV9FQ7hPMYenOald5VP6PcemOA aczBb0TpKbfhSnpMSKs4YWUoZ9GuvwYFSq/i2RUuHkc5NH3jNtgF1OqR6RU8SkIxpAn7 YGO+ixvJxXT676CDdqhJtSzs9R1nFHgHzbNCEB4RajPKscQeNHOwJPjNkPp/Qr4+S9te wh7XHsHOhgAoVU9F3XiikZH2Ghh2qV4d5VLFoiFgSGLOflvRjOB8b7hXS7f+IqQJWVEt DcrFA9atze2D89iaKC8mrU7PNeki9/O9NxttO5TfZQzDHjEqBDNVs+dxylB8c3V0FdxX P+WA== X-Received: by 10.182.114.132 with SMTP id jg4mr20904533obb.29.1390764157753; Sun, 26 Jan 2014 11:22:37 -0800 (PST) Original-Received: by 10.76.79.102 with HTTP; Sun, 26 Jan 2014 11:22:37 -0800 (PST) In-Reply-To: <8761p7uykd.fsf@maru2.md5i.com> X-Google-Sender-Auth: 8_bsFo_VjvWmlkVD1w41rIYdjBM X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c01::22f 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:169140 Archived-At: --001a11c329a296eaa104f0e483fa Content-Type: text/plain; charset=UTF-8 While we're at it - why not increase the default `gc-cons-threshold' as well. Currently the default is 0.8 MB, which seems super-conservative given today most computers have 1GB+ of memory. Code that creates a lot of objects would obviously be impacted significantly, since GC would be performed frequently. Setting it to something in between 10MB and 50MB seems much more reasonable to me. On 26 January 2014 07:00, Michael Welsh Duggan wrote: > Tom writes: > > > Drew Adams oracle.com> writes: > >> > >> BTW, whether someone finds a history list of 1000 elements to be > >> long or reasonable might also have to do with how they access its > >> elements. > >> > >> If someone typically just cycles among elements using, say, `M-p', > >> instead of searching (using, say, `M-r') or completing, then 1000 > >> would generally be far too long a list - as would even 100 probably. > >> (I tend to complete against the history list.) > > > > All users should know at least M-r, it's in the manual, so it > > should be no argument against a longer history list. > > FWIW, I've been using emacs for many, many years, and did not know about > M-r. On the other hand, I don't object to increasing the history size, > because now I know about M-r! Thanks! > > -- > Michael Welsh Duggan > (md5i@md5i.com) > > --001a11c329a296eaa104f0e483fa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
While we're at it - why not increase the default `gc-c= ons-threshold' as well. Currently the default is 0.8 MB, which seems su= per-conservative given today most computers have 1GB+ of memory. Code that = creates a lot of objects would obviously be impacted significantly, since G= C would be performed frequently. Setting it to something in between 10MB an= d 50MB seems much more reasonable to me.=C2=A0


On 26 January= 2014 07:00, Michael Welsh Duggan <mwd@md5i.com> wrote:
Tom <adatgyujto@gmail.com> writes:

> Drew Adams <drew.adams <at> oracle.com> writes:
>>
>> BTW, whether someone finds a history list of 1000 elements to be >> long or reasonable might also have to do with how they access its<= br> >> elements.
>>
>> If someone typically just cycles among elements using, say, `M-p&#= 39;,
>> instead of searching (using, say, `M-r') or completing, then 1= 000
>> would generally be far too long a list - as would even 100 probabl= y.
>> (I tend to complete against the history list.)
>
> All users should know at least M-r, it's in the manual, so it
> should be no argument against a longer history list.

FWIW, I've been using emacs for many, many years, and did n= ot know about
M-r. =C2=A0On the other hand, I don't object to increasing the history = size,
because now I know about M-r! =C2=A0Thanks!

--
Michael Welsh Duggan
(md5i@md5i.com)


--001a11c329a296eaa104f0e483fa--