On Saturday 27 June 2009 18:32:05 Detlev Offenbach wrote: > On Samstag, 27. Juni 2009, Henrik Pauli wrote: > > On Saturday 27 June 2009 17:11:11 you wrote: > > > On Samstag, 27. Juni 2009, Henrik Pauli wrote: > > > > Now that this thing works in my distro, here's what I found odd: > > > > > > > > I set indentation to tabsize=4 indentsize=4 usetabs. Yet, tabs are 2 > > > > characters wide. I do use a monospaced font so it shouldn't be a > > > > confusion with variable width... I remember this issue from back in > > > > the days when I wrote ljKlient. > > > > > > The shell and the terminal are using the QScintilla highlighter setup > > > like the editor. Did you configure these. > > > > Sorry, the tabsize issue was in the editor, I forgot to emphasise that. > > I don't care about tab size in the shell or the terminal. > > Did you configure the highlighters? (Editor->Highlighters->Styles, > Python,...)
They're left on default but they only affect colours and font type/size, not tab properties. 'Use monospaced font by default' overrides all fonts into monospace (apparently), and so those shouldn't matter, I think > > > > > Shell and terminal fonts look huge, apparently 10pt or so, regardless > > > > of me setting it to 8pt (laptop screen estate is very scarce, > > > > afterall > > > > > > > > :)) > > > > > > What and where did you set to 8pt (might be the same issue as above) > > > > Settings/Editor/Style, Monospaced font, Use monospaced font as default > > That has an effect in the editor only. Shall this be extended to the shell > and terminal? I guess it would be a good idea to make it possible to set fonts for those, in one way or another :) > > > > > Also, I have some ANSI colour escape sequences in my PS1, which show > > > > up in the terminal as ESC[32;01m etc. instead of colours, or getting > > > > stripped. Not sure if this is a known issue. > > > > > > The eric4 terminal is not a full terminal emulation. That means, ANSI > > > escape sequences are not supported. However, patches are welcome. > > > > Stripping them might be a good idea: > > s/\e\[[\d;]*[\w]//g; > > > > unless I'm mistaken :) (this is how I'd do it in Perl, not sure what I'd > > do in Python exactly, it's been a while) > > I'll look into that. > > Detlev _______________________________________________ Eric mailing list Eric@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/eric