From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Garreau, Alexandre" <galex-713@galex-713.eu>
Cc: emacs-org list <emacs-orgmode@gnu.org>, Amin Bandali <bandali@gnu.org>
Subject: Re: org-store/insert-link truncating the full subject of mails
Date: Fri, 02 Nov 2018 01:55:06 +0100 [thread overview]
Message-ID: <87k1lw9u39.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871s8a1xrl.fsf@portable.galex-713.eu> (Alexandre Garreau's message of "Sun, 28 Oct 2018 05:49:18 +0100")
Hello,
"Garreau, Alexandre" <galex-713@galex-713.eu> 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’t
> and only did partially for org, yet… but for instance I did for Gnus, 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,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-11-02 0:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 5:30 org-store/insert-link truncating the full subject of mails Garreau, Alexandre
2018-10-26 15:35 ` Nicolas Goaziou
2018-10-26 15:42 ` Garreau, Alexandre
2018-10-26 19:54 ` Nicolas Goaziou
2018-10-26 23:22 ` Amin Bandali
2018-10-27 9:27 ` Nicolas Goaziou
2018-10-27 10:43 ` Garreau, Alexandre
2018-10-27 11:55 ` Nicolas Goaziou
2018-10-28 4:49 ` Garreau, Alexandre
2018-11-02 0:55 ` Nicolas Goaziou [this message]
2018-10-28 4:49 ` Garreau, Alexandre
2018-10-28 14:05 ` Amin Bandali
2018-10-28 17:01 ` Garreau, Alexandre
2018-10-28 19:23 ` org-email-link-description-format (Was: Re: org-store/insert-link truncating the full subject of mails) Garreau, Alexandre
2018-10-29 7:30 ` org-store/insert-link truncating the full subject of mails Eric S Fraga
2018-10-30 15:42 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1lw9u39.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bandali@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=galex-713@galex-713.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).