From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>, 34183@debbugs.gnu.org
Cc: Gemini Lasswell <gazally@runbox.com>
Subject: bug#34183: 27.0.50; cl-print uses print-length for strings
Date: Wed, 23 Jan 2019 13:48:29 -0800 (PST) [thread overview]
Message-ID: <b1529a87-1cee-48a5-86b6-d03a74623434@default> (raw)
In-Reply-To: <jwv4l9z2j3t.fsf@iro.umontreal.ca>
> The code in cl-print now obeys `print-length` to limit the length of
> strings. Being able to limit the length of strings is good, but
> limiting them to `print-length` chars is rather drastic since this
> setting is usually applied to lists, where a setting of N corresponds to
> an output that's at the very least 2*N long (assuming each element prints
> as a single char, which is not the most common case).
>
> Currently in M-: print-length defaults to 12, so any string like a file
> name gets truncated after only 12 chars which is frustrating
> (especially since the ability to expand the "..." doesn't work there
> because you can't click in the echo area :-( Maybe that should be
> another bug report / feature request).
>
> We should probably introduce another config var to limit string length,
> or multiply `print-length` by some ad-hoc factor (like 4 maybe), or use
> the max of print-length and frame-width, ...
Why don't we have a naming convention that lets users
know whether some function is (1) intended to emulate
a Common Lisp function or it is instead either just
(2) a helper function used to define such an emulation
function or (3) a function that has no relation to
Common Lisp, which someone (unfortunately) decided to
give the prefix `cl-'? Things that have prefix `cl-'
seem to be all over the map.
Anyway, in Common Lisp the print functions (which we
apparently have no emulations for) take arguments that
control print length, circle handling etc. They don't
just variables to control such things.
http://clhs.lisp.se/Body/f_wr_pr.htm
prev parent reply other threads:[~2019-01-23 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 20:51 bug#34183: 27.0.50; cl-print uses print-length for strings Stefan Monnier
2019-01-23 21:48 ` Drew Adams [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1529a87-1cee-48a5-86b6-d03a74623434@default \
--to=drew.adams@oracle.com \
--cc=34183@debbugs.gnu.org \
--cc=gazally@runbox.com \
--cc=monnier@IRO.UMontreal.CA \
/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.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).