From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: Amin Bandali <bandali@gnu.org>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: org-store/insert-link truncating the full subject of mails
Date: Sat, 27 Oct 2018 12:43:02 +0200 [thread overview]
Message-ID: <87lg6j3c21.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <87zhuzd9ih.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 27 Oct 2018 11:27:50 +0200")
Le 27/10/2018 à 11h27, Nicolas Goaziou a écrit :
> Hello,
>
> Amin Bandali <bandali@gnu.org> writes:
>
>> Can you please elaborate on what you mean by being on the safe
>> side in this context? What problems could potentially arise from
>> returning the subject in full length?
>
> I don't know. This is why I agree it is safer to limit length to an
> arbitrary number instead of allowing any size.
Without justification, that’d look like “argument from ignorance”, so
unless a real reason is found, I believe it would be better to remove a
truncation that will very certainly in fact bother at least some users
(while there’s still 0 data point on how non-truncation might be
bothering, and that’s what being asked).
next prev parent reply other threads:[~2018-10-27 10:43 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 [this message]
2018-10-27 11:55 ` Nicolas Goaziou
2018-10-28 4:49 ` Garreau, Alexandre
2018-11-02 0:55 ` Nicolas Goaziou
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=87lg6j3c21.fsf@portable.galex-713.eu \
--to=galex-713@galex-713.eu \
--cc=bandali@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).