[Maxima-commits] [git] Maxima CAS branch, master, updated. branch-5_31-base-183-gf44d669

On 2013-12-05, Rupert Swarbrick <rswarbrick at gmail.com> wrote:

> I didn't realise the commits were potentially controversial - I would
> have asked on the mailing list first if I had.

For the record, I don't believe it's necessary to get support for all
changes before committing something. We can use the revision control
system to revert changes after the fact. I don't mean to suggest that
developers can ignore the opinions of others, only that an occasional
reversion is an acceptable price to pay for getting more work done.

> I intentionally didn't try to use *prompt-prefix* and *prompt-suffix*
> here because I know that they are designed for front-ends to "tag" their
> prompts easily. Since they are just strings, I couldn't think of a way
> to add a note after the prompt without potentially clobbering them. But
> maybe I missed something?

I dunno, I'm not convinced the prompt note system is useful enough.
I can see that being able to rework the prompts is going to be useful
for people writing user interfaces -- agreed on that point. But isn't
it enough for that purpose to concentrate the prompt formatting into
a single function (as in the previous commit, which, as I said, is OK
by me) which can then be replaced easily enough? We could even make the
prompt formatter a Maxima function so that it can be replaced by Maxima
code.

best,

Robert Dodier