[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: DOCBOOK-APPS: Re: Markup for shell-like typescripts
>>>>> "Norman" == Norman Walsh <ndw@nwalsh.com> writes: Norman> / Jochen Hein <jochen@jochen.org> was heard to say: | I'd Norman> like to mark something like (unchecked): | | <figure> Norman> <title>an simple example</title> <screen> | Norman> <computeroutput>bash#</computeroutput> <userinput>echo input Norman> | sed -e | <computeroutput>'s/in/out/'</userinput> Norman> output</computeroutput> Norman> One simple answer would be to present the screen without Norman> additional markup. Or are you making presentation Norman> distinctions between these? Yes, I like to have a distinct representation. In legacy documents I have I use bold for userinput, and have LaTeX commands for shell prompts, input and output representation. And I like that represention. Norman> | This works fine with %number-screen-lines% set to #f or Norman> short | listings. I do have (define %number-screen-lines% Norman> #t) which messes it | up in longer examples (line numbers are Norman> missing, text bounces to the | left and back). Norman> Short example that demonstrates the problem, please. Here we are. JochenTitle: Test 1
-- Nicht weil die Dinge schwierig sind, wagen wir sie nicht, sondern weil wir sie nicht wagen, sind sie schwierig.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC