all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 15375@debbugs.gnu.org
Subject: bug#15375: 24.3.50; Elisp manual: mention what units are used for window margin functions
Date: Sat, 14 Sep 2013 08:18:38 -0700 (PDT)	[thread overview]
Message-ID: <56620f72-f813-4a5b-b6bc-3b543ebb8e50@default> (raw)
In-Reply-To: <<8361u3hhwn.fsf@gnu.org>>

> > (elisp) `Display Margins` talks a lot about window margins, but AFAICT
> > it never once says which units are used for the functions and variables
> > described there.  I'm guessing the unit is `frame-char-width', but Emacs
> > should tell us explicitly here.
> 
> The units are character cells (a.k.a. "columns").
> 
> I fixed this in trunk revision 114279.
> 
> > Moreover, we don't even tell users what a nil value means, as opposed
> > to a whole number.
> >
> > For example, right now, `M-: (window-margins)' returns `(nil)' for me,
> > which corresponds to both LEFT and RIGHT being nil.  What does a nil
> > value mean for each of these?
> 
> Fixed that as well.

Thanks.  Do you want me to close the bug, or do you want to?
(Dunno whether you wanted to keep it open for some reason.)





       reply	other threads:[~2013-09-14 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<eaf7fceb-d02d-4cd9-9b52-e815d4c47926@default>
     [not found] ` <<8361u3hhwn.fsf@gnu.org>
2013-09-14 15:18   ` Drew Adams [this message]
2013-09-14 15:29     ` bug#15375: 24.3.50; Elisp manual: mention what units are used for window margin functions Eli Zaretskii
     [not found] <<56620f72-f813-4a5b-b6bc-3b543ebb8e50@default>
     [not found] ` <<83ob7vfmlb.fsf@gnu.org>
2013-09-14 16:26   ` Drew Adams
2013-09-14 16:33     ` Eli Zaretskii
2013-09-13 22:17 Drew Adams
2013-09-14  9:27 ` Eli Zaretskii

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=56620f72-f813-4a5b-b6bc-3b543ebb8e50@default \
    --to=drew.adams@oracle.com \
    --cc=15375@debbugs.gnu.org \
    --cc=eliz@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 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.