emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: merging etc


From: joakim
Subject: Re: merging etc
Date: Thu, 30 Aug 2007 15:02:35 +0200
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1.50 (gnu/linux)

David Kastrup <address@hidden> writes:

> Stefan Monnier <address@hidden> writes:
>
>>> Just to get things started, here is a tentative NEWS entry:
>>
>>> ** Emacs now supports several simultaneous display devices.
>>> Emacs can now handle frames on several different X displays and
>>> terminals simultaneously. Emacsclient has also been extendend to allow
>>> specification on which display to use.
>>
>> That's the Emacs-level documentation.
>
> It is?  We don't need to document that environment variables suddenly
> are session-specific, we don't need to document the relation of
> sessions to frames to terminals and so on?  That some stuff has become
> frame-local, too?

Is that sort of thing normaly documented in NEWS? I thought the
purpose of NEWS was to be a somewhat terse overview?

> I think that some of those details would better be solved in a
> different way, but it is not easy to do or judge that if the current
> choices are not really documented with their user-relevant
> consequences.
>
>> We need the Lisp-level doc as well.
>
> That too.  But for discussing and/or cleaning the implications of the
> design, the consequences for the user are of foremost interest, I
> think.  If we can't explain the consequences for the user concisely
> and understandably, there is a problem with the design.
>
> So that is the kind of documentation I would want to see first.  If
> the user-visible consequences are easy to understand and consistent,
> the documentation for _that_ can stay, and the Lisp level can then try
> to follow.
>
> -- 
> David Kastrup

-- 
Joakim Verona




reply via email to

[Prev in Thread] Current Thread [Next in Thread]