From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org-store/insert-link truncating the full subject of mails Date: Fri, 02 Nov 2018 01:55:06 +0100 Message-ID: <87k1lw9u39.fsf@nicolasgoaziou.fr> References: <875zxpi8bn.fsf@portable.galex-713.eu> <87k1m4g1qk.fsf@nicolasgoaziou.fr> <87woq4pveb.fsf@portable.galex-713.eu> <874ld8fpqf.fsf@nicolasgoaziou.fr> <87in1ojntq.fsf@aminb.org> <87zhuzd9ih.fsf@nicolasgoaziou.fr> <87lg6j3c21.fsf@portable.galex-713.eu> <87r2gbd2oz.fsf@nicolasgoaziou.fr> <871s8a1xrl.fsf@portable.galex-713.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45556) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gINkT-00047C-Mg for emacs-orgmode@gnu.org; Thu, 01 Nov 2018 20:55:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gINkL-0003Z0-Nu for emacs-orgmode@gnu.org; Thu, 01 Nov 2018 20:55:37 -0400 In-Reply-To: <871s8a1xrl.fsf@portable.galex-713.eu> (Alexandre Garreau's message of "Sun, 28 Oct 2018 05:49:18 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: "Garreau, Alexandre" Cc: emacs-org list , Amin Bandali Hello, "Garreau, Alexandre" writes: > This is an argument in favor of immobility. True. Immobility is sometimes good, too. > Yes, if only each user of each piece of software took the time to read > the integrality of documentation each time they used something: I don=E2= =80=99t > and only did partially for org, yet=E2=80=A6 but for instance I did for G= nus, a > long time ago, and never did it again: as example, did you?. I don't see the point of reading the whole manual when you are looking for some specific information. You can use, e.g., indices for that. > Default are an important thing, they should fit what the most common, > unspecific, and ignorant about the software in question, person. > Documentation should be there only to adapt to more specific, and less > common, cases (and, when possible, software should be made so that to > conditionally do the right thing depending of the context so that > changing the default behavior is less and less needed). Not the other > way around. These are good rules of thumb when you are defining a default value. When the default value was set ages ago, and some users may have grown habits on it, you have to strike a balance between usage and theory. To put it differently, changing default values annoys some users, and a better default value may not be worth it. It seems that no one is firmly attached to the current default value, so I removed the truncation in "next" branch, i.e., Org 9.3. Regards, --=20 Nicolas Goaziou