>>>>> "Edmar" == Edmar Wienskoski <[EMAIL PROTECTED]> writes:
Edmar> I had another idea:
Edmar> 1 - We define Scrap as a paragraph. Which implies that will be
Edmar> no need to patch anything.
Edmar> 2 - The code segments must be typed with c-return at each code
Edmar> line. Which implies that no empty lines will be outputed.
Edmar> 3 - Since we are using c-return, it is expliciity that the
Edmar> lines will not be separated. Which implies that no
Edmar> undocumented feature is being used!!! (right ?)
That's exactly what I had in mind. As long as you use 'Newline 0' and
'Freespacing 1', everything should be alright.
Edmar> My work stops here. The problem is solved in a clean way.
Edmar> In the feature... If the programmers complain they don't like
Edmar> to type c-ret, he can change his bindings to swap the ret and
Edmar> c-ret keys. We can also help by making this binding dynamic.
Edmar> (Emacs has this, when you change mode, some key bindings also
Edmar> change) That would be a new feature to describe what the key
Edmar> bindings are within each layout. The Scrap layout usage would
Edmar> then be improved by using this new feature to swap the bindings
Edmar> for ret and c-ret.
Well, I think that the fact that Return separates different entities
is right (different paragraphs), and having Return be in fact
Ctrl-Return is not necessarily a good thing. However, a solution could
be a KeepParagraphsTogether option to avoid unwanted paragraph breaks.
In the long term, I suggest that you (or somebody else) implement a
noweb inset which takes care of outputing the <<...>>= and the final
@, and makes sure that the lines come out correctly. This should not
be too difficult in 1.1.x.
JMarc
