Juergen Vigna <[EMAIL PROTECTED]> writes:
| Well Lars you should point on your nose first before saying such a thing
| and second I seem to have read in a mail that we are still in a cvs tree
| and not a released one so "errors are allowed".
I am not pointing at you, but it is a fact and we have seen this a
number of times: regardless of how little we/you/I change, there are issues
that we/you/I did not think of. And sure "errors are allowed".
| > One idea(probably too simplistic), would be to use the old behaviour,
| > but let the "newfile" be a unique filename so that you wont get
| > clashes. This would owever mean that you would have to press RETURN
| > one time after File->New (or click ok). I tink I could agree on this
| > being a lyxrc variable: \new_file_default_ok. You would set this to
| > true I would set it to false. Would that work?
| >
|
| Well I really don't get it what you really mean here and here you ask
| for a lyxrc variable while above you said this is out of question.
You solution uses a totally different scheme for the two cases, mine
is exactly the same in both cases modulo the dir-popup.
| Well look at the last commit I did I hope you like this approach, we
| can do a "User poll" for the default behaviour on the User-List if you
| want.
|
| > This would mean _no_ special handling at all, and the variables you
| > introduced in Buffer could be removed.
|
| Well this special variables ARE needed anyway as I don't want autosaving
| for temporary new files I did not name!
Why care about this? Make make this special case? What are the
benefits? (and what are the drawbacks?)
Do you _always_ give the document a name at once if you plan to keep
the file? Or are your wont to loose data unless you have remembered to
rename the document?
Lgb
