Re: need obsolete arg in (read-from-minibuffer ...)

[ken]

On 03/18/2011 04:37 PM Drew Adams wrote:
>> the docs say that 2nd arg is obsolete.  However,
>> I've tried a lot of permutations of the args listed and I 
>> can't get this function to work without using that obsolete 2nd arg.
>> (defun mygetstr (def-val)
>>     (read-from-minibuffer "Enter/Edit string: "
>>                           def-val nil nil nil def-val t))
> 
> What do you mean by "work"?  And what do you mean "without" the obsolete arg?

Sorry, I should have been clearer.  If I change the 2nd arg from
"def-val" to "nil", then def-val isn't displayed in the minibuffer for
editing by the user.  However, the docs say that this arg is obsolete.
I take this to mean that it should be left as "nil".


> That argument must be present if you include any arguments to the right of it.

That's correct.


> 
> What is considered (by some) to be "obsolete" is to use a non-nil value for 
> the
> argument.  That's all.  You cannot simply remove the arg if you include args
> such as the DEFAULT-VALUE and INHERIT-INPUT-METHOD.  A nil argument can be
> omitted if there are no non-nil args coming after it (i.e., to the right).

I agree.