mailing-list for TeXmacs Users

[Henri Lesourd <address@hidden>]

Dennis Heuer wrote:

> > Document->Spacing->Interline separation is your friend.
> >    
>
> there is no such path.
Sorry, in fact it's :
Document->Paragraph->Spacing->Interline separation


> am i stucked in a mode again (i re-opened texmacs
> but nothing changed in 'document'). interestingly, when the bottom of
> the page is reached, new lines are pushing up the previous lines until
> a certain line spacing is reached and the next page is created. i
> find this behaviour quite weird. at least, i don't need it for nothing.
>
>  
Yes, this is an annoyance, usually editors scroll one
line at a time, while TeXmacs scrolls half a page. To
be improved in the future.


> btw., texmacs could profit from the new clipboard protocol of the
> freedesktop initiative. it would make sharing (formatted) input easier
> between 'modern' apps and texmacs.
>
>  
Thanks for the pointer.


> the question is not if the editor is structured. the
> question is if this aspect should be in the way most of the time. there
> are some cases when the discussed behaviour is useful. this are those
> cases when the text structure is in focus. in the most cases, i.e. when
> moving around the cursor or when clicking into the text, the discussed
> behaviour is in the way. this is why this behaviour should be activated
> intentionally and not all the time. this is rather a question of HCI or
> heuristics.
>
>  
Not false.


> as far as i understand, the light-blueish outline shows one block of
> specific format/settings (a paragraph with own font settings, a bold
> text sequence, etc.). what i don't understand is how to clean up ugly
> formatted text again, i.e. how to get two blocks compatible again to
> make them one block without copying over the content of one block into
> the other. i first tried to just delete the space between the blocks but
> that didn't help. then i tried the source view but it doesn't allow me
> to delete a definition without deleting its subordinated content too.
>
>  
OK, I see. Yes, handling of redundant markup could
be improved, although, there is already a certain
number of things already done.


> do i have to activate something to make
> texmacs aware of the new fonts? why there are more fonts available in
> 'format' than in 'document'?
>
>  
TeXmacs is not like word where you can choose a font by means of
its name. There is some kind of underlying logic to classify the
available fonts in more abstract categories, it seems. But I don't
know how it works exactly, in fact. What I know is that (to my
knowledge), the raw name of the font never appears in the markup.


> i urge you to support 'modern' infrastructures like freetype and
> fontconfig.
TeXmacs fully supports Freetype.


> but also the toolkit's own open and save dialogs (texmac's
> dialogs don't show umlauts correctly. the save dialog doesn't like
> colons and umlauts in filenames.) same for stack icons and theme
> support, etc. the latter both are easier supportable than one may think
> (see freedesktop.org).
>
>  
This is gonna improve soon, we are currently redoing
the gui (i.e., menus, filechooser, and the like). In
some months, everything will be completely different
in this respect.


> > Fonts with a type 1 equivalent on your harddisk will be vectorized for sure.
> >    
>
> all my fonts are truetype :(
>
>  
Isn't Type 1 the same as truetype ?


> the document was located at a different path (my document folder) than
> the shown path. the path in the window bar explicitly targeted to a
> temporary version (with a code in the name) in the temporary space of
> texmacs.
>
>  
Strange. Usually you do File->Export->Pdf, and then it creates
a PDF file in directory where your file is located, and you
don't have these name problems.


> i also tried the fullscreen mode but couldn't leave anymore (had to
> crash X). there was a context menue available at right-click--but
> without context. the entries do not react to clicking on them. there
> doesn't even pop up an empty submenue.
>
>  
This should definitely work. What OS are you using ?