From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Rankin <hello@paulwrankin.com>, 29597@debbugs.gnu.org
Subject: bug#29597: 26.0.90; line-number-display-width returns incorrect width
Date: Fri, 8 Dec 2017 17:39:09 -0500 [thread overview]
Message-ID: <CAM-tV-8jzjsGB1msdLQrJCNmFtSm4ks3dMuEf4BdTn6nTR6Yhw@mail.gmail.com> (raw)
In-Reply-To: <83zi6tuqsv.fsf@gnu.org>
On Fri, Dec 8, 2017 at 11:29 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Noam Postavsky <npostavs@users.sourceforge.net>
>> Date: Fri, 8 Dec 2017 11:23:18 -0500
>> Cc: Paul Rankin <hello@paulwrankin.com>, 29597@debbugs.gnu.org
>>
>> > I don't object to such trivial wrappers, although I'd raise a brow if
>> > I saw something like this in Emacs. It sounds too trivial to have 2
>> > more symbols in the name-space. But that's me.
>>
>> Is the symbol space really a scarce resource?
>
> Not really scarce, but do you really feel good with such trivial
> wrappers? Do we have anything similar anywhere else?
Flag parameters are pretty common in Emacs, but it doesn't make me
feel better about them.
I feel pretty okay about wrappers. For other examples, string-match-p
is a fairly trivial wrapper around string-match.
next prev parent reply other threads:[~2017-12-08 22:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 5:34 bug#29597: 26.0.90; line-number-display-width returns incorrect width Paul Rankin
2017-12-07 8:55 ` Eli Zaretskii
2017-12-08 1:44 ` Paul Rankin
2017-12-08 2:00 ` Noam Postavsky
2017-12-08 2:32 ` Paul Rankin
2017-12-08 15:01 ` Eli Zaretskii
2017-12-08 15:37 ` Noam Postavsky
2017-12-08 15:53 ` Eli Zaretskii
2017-12-08 15:55 ` Eli Zaretskii
2017-12-08 16:23 ` Noam Postavsky
2017-12-08 16:29 ` Eli Zaretskii
2017-12-08 22:39 ` Noam Postavsky [this message]
2017-12-08 14:22 ` Eli Zaretskii
2017-12-08 14:40 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-8jzjsGB1msdLQrJCNmFtSm4ks3dMuEf4BdTn6nTR6Yhw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=29597@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hello@paulwrankin.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.