From: Koblinger E. <eg...@su...> - 2002-01-31 22:22:51
|
Hi, Two issues about joerc file: 1. It lacks bol ^[[H, bol ^[[1~, eol ^[[F, eol ^[[4~ entries. Older joerc's had it, as well as current jpicorc/others have it, too. This make Home/End unusable in xterm by default. 2. I generally hate if someone wants to force his personal preferences to other people, but now this situation might be different. :) The topmost line has a "%t" item to display the current time. I really doubt if anyone uses it, there's a command "date", there's a clock on most people's desktop, and it's not the job of a text editor to display the time. Furthermore, in multiple window mode you can see the current time multiple times, wasting lots of space on the screen. Instead, displaying the percent where the cursor is, is really useful, helps editing long texts, and this is something a text editor should really do. So, if everyone agrees, I recommend replacing "%t" by "%p%%" in "-rmsg". bye egmont |
From: Xavier N. <nic...@ef...> - 2002-01-31 22:51:18
|
On Thu, Jan 31, 2002 at 11:22:35PM +0100, Koblinger Egmont wrote: > Two issues about joerc file: > 1. It lacks bol ^[[H, bol ^[[1~, eol ^[[F, eol ^[[4~ entries. Older > joerc's had it, as well as current jpicorc/others have it, too. > This make Home/End unusable in xterm by default. This is probably a good idea, but it doesn't work for me with joe 2.8 (Mandrake 8.0) and Eterm. Does bol .kh and eol .kH should work ? > So, if everyone agrees, I recommend replacing "%t" by "%p%%" in "-rmsg". I personnaly agree, because it is always good to know where you are in a text. I have also some problems with the compiling features of joe: I use ESC c to compile, then I write 'make' Then joe open a new window with the result of the make. * The first problem is: we must ctrl+c this window to close it, and joe asks for confirmation since it is a new window (which is annoying). If we compile several times, joe will open several windows for each make. * I use ESC = to navigate across the errors, which is VERY cool ! But joe does not go directly to the first error: it opens a g window which is empty. I suppose joe wants gcc and I compile with g++. I don't know where to change this (I have been looking uerror.c without understanding anything). I wonder if someone has encountered such pb and if he/she found any solution. Moreover, I didn't find where the man page deals with it. -- Nicollet Xavier I2 Info EFREI Linux: http://www.linux.efrei.fr/ Le piratage tue le libre |
From: Vitezslav S. <sa...@ma...> - 2002-02-04 13:42:55
|
Hi! > > 1. It lacks bol ^[[H, bol ^[[1~, eol ^[[F, eol ^[[4~ entries. Older > > joerc's had it, as well as current jpicorc/others have it, too. > > This make Home/End unusable in xterm by default. > > This is probably a good idea, but it doesn't work for me with joe > 2.8 (Mandrake 8.0) and Eterm. > Does bol .kh and eol .kH should work ? Maybe it's time to have correct terminfo databases. ^[[H, ^[[1~, ^[[F, ^[[4~ entries are only for those of you, who don't have correct terminfo db. If you want the Home and End keys set system-wide (for all r insert) applications which uses terminfo) change khome and kend entries in your terminfo DB. Meanwhile I should either put those entries back into joerc or place some "BIG FAT WARNING" into README about those issues. (On my system I found another xterm terminfo definition named xterm-new: try `TERM=xterm-new joe` and tell me if Home and End keys work for you now. To Egmont: according to your address you have slightly more power than me to convince large Linux distribution to have xterm-new to be xterm as default.) > > So, if everyone agrees, I recommend replacing "%t" by "%p%%" in "-rmsg". > > I personnaly agree, because it is always good to know where you are > in a text. > > > I have also some problems with the compiling features of joe: > > I use ESC c to compile, then I write 'make' > Then joe open a new window with the result of the make. > > * The first problem is: we must ctrl+c this window to close it, and joe asks > for confirmation since it is a new window (which is annoying). If we compile > several times, joe will open several windows for each make. > > * I use ESC = to navigate across the errors, which is VERY cool ! But joe does > not go directly to the first error: it opens a g window which is empty. I > suppose joe wants gcc and I compile with g++. I don't know where to change > this (I have been looking uerror.c without understanding anything). > I wonder if someone has encountered such pb and if he/she found any > solution. The first help is to run make with -s switch: it suppress all unwanted output. But this doesn't cure it all: as I tested it, it still has problems with some error output. > > Moreover, I didn't find where the man page deals with it. Maybe you could write about it and it to us ;-)) Cheers, Vita |
From: Xavier N. <nic...@ef...> - 2002-02-04 16:34:11
|
On Mon, Feb 04, 2002 at 02:42:41PM +0100, Vitezslav Samel wrote: Thank you for the make -s tip > > Moreover, I didn't find where the man page deals with it. > Maybe you could write about it and it to us ;-)) As I didn't know it well, I expected someone to explain it :) But you're right, I'd better write a little text which could be inserted into the man-page. BTW, is it planned to write some documentation with linux-doc or DocBook ? I personnaly use DocBook. As it is often painfull to write all the markups, here are my joerc macros for DocBook: "<title></title>",prevword,prevword,nextword,rtarw .k1 "<para>",rtn,"</para>",uparw,rtn,"\x09" .k2 "<programlisting>",rtn,rtn,"</programlisting>",uparw,ltarw .k3 "<emphasis></emphasis>",prevword,prevword,nextword,rtarw .k4 "<itemizedlist>",rtn,"\x09<listitem> <para>",rtn,"</para> </listitem>",rtn,backs,"</itemizedlist>",uparw,bol,rtn,uparw,"\x09\x09" .k5 "<listitem> <para>",rtn,"</para> </listitem>",bol,rtn,uparw,"\x09" .k6 "<filename></filename>",prevword,prevword,nextword,rtarw .k7 "<procedure>",rtn,"\x09<step> <para>",rtn,"</para> </step>",rtn,bol,"</procedure>",uparw,uparw,eol,rtn,"\x09" .k8 "<step><para>",rtn,"</step></para>",uparw,rtn,"\x09" .k9 "<![CDATA[",rtn,"]]>",prevword,rtn,uparw .k0 You can use the F1-F10 keys to make it work -- Nicollet Xavier I2 Info EFREI Linux: http://www.linux.efrei.fr/ Le piratage tue le libre |
From: Mikhael G. <mi...@ho...> - 2002-02-04 23:20:05
|
On 04 Feb 2002 17:34:03 +0100, Xavier Nicollet wrote: > > On Mon, Feb 04, 2002 at 02:42:41PM +0100, Vitezslav Samel wrote: > > BTW, is it planned to write some documentation with linux-doc or DocBook ? > > I personnaly use DocBook. As it is often painfull to write all the markups, > here are my joerc macros for DocBook: > > "<title></title>",prevword,prevword,nextword,rtarw .k1 I hope you know that this binding does not work as expected with 2.9.x. The meaning of prevword and nextword was changed in new versions. I would _really_ like if this is fixed. Having prevfullword/nextfullword would be preferable, but the meaning of prevword/nextword should not be changed, otherwise as it is now a lot of configs are broken. I have several such bindings in my rc file that are broken with 2.9.x. Regards, Mikhael. |
From: Moritz B. <bar...@gm...> - 2002-02-05 08:07:40
|
Hi and good morning, On Mon, Feb 04, 2002 at 23:18:53 +0000, Mikhael Goikhman wrote: > I would _really_ like if this is fixed. Having > prevfullword/nextfullword would be preferable, I totally agree. At least some people _need_ the previous behavior, be it with new keywords or with the old ones. E.g. for editing (other people's ;->) C source code without a single whitespace per line. Going to the intermediate characters is a real PITA. > but the meaning of prevword/nextword should not be changed, otherwise > as it is now a lot of configs are broken. I guess you're right there. My next patch would've been to at least optionally have the old behavior back (e.g. via ./configure). Hoping, Moritz :) |
From: Mikhael G. <mi...@ho...> - 2002-02-05 09:47:28
|
On 05 Feb 2002 09:07:31 +0100, Moritz Barsnick wrote: > > On Mon, Feb 04, 2002 at 23:18:53 +0000, Mikhael Goikhman wrote: > > > I would _really_ like if this is fixed. Having > > prevfullword/nextfullword would be preferable, > > I totally agree. At least some people _need_ the previous behavior, be > it with new keywords or with the old ones. Just to clarify myself, my proposed meanings of "word" and "fullword" (or "extword") are: (Congratulations,=programmers,./+,.on-this-list) ||<----word--->| |<--word->| | | | |<-------- full word, or extended word ------->| The "word" definition may be optionally dependent on a user's locale or just be what it was in the past. Regards, Mikhael. |
From: Vitezslav S. <sa...@ma...> - 2002-02-07 08:48:45
|
> Hi and good morning, > > On Mon, Feb 04, 2002 at 23:18:53 +0000, Mikhael Goikhman wrote: > > > I would _really_ like if this is fixed. Having > > prevfullword/nextfullword would be preferable, > > I totally agree. At least some people _need_ the previous behavior, be > it with new keywords or with the old ones. E.g. for editing (other > people's ;->) C source code without a single whitespace per line. Going > to the intermediate characters is a real PITA. > > > but the meaning of prevword/nextword should not be changed, otherwise > > as it is now a lot of configs are broken. > > I guess you're right there. > > My next patch would've been to at least optionally have the old > behavior back (e.g. via ./configure). I prefer to back out to the original behaviour unless better solution is found (and coded and sent to maintainers) - Marek wants to have a rc-file option to set which chars can be in word and which cannot. Cheers Vita |
From: Xavier N. <nic...@ef...> - 2002-02-10 22:39:34
Attachments:
joe.1.in.diff
|
Hi all, I have written a small paragraph in the man page on howto compile. Since I am not a native English speaker, I would apreciate than some of you re-read it. Here is what is seen on the screen during a man joe: Shell windows Hit ^K ' to run a command shell in one of JOE's windows. When the cursor is at the end of [...] the shell is killed. Compiling features You can use JOE to compile your programs and parse errors if any. Hit ^[ C to compile your sources. JOE prompts you for a command. Type "make -s" for example. Then a window shows you all the warnings. You can hit ^[ = to navigate to the next error and ^[ - to go to the previous error. The current error/warning is displayed at the bottom of the screen. Cor- responding files are automatically loaded. Environment variables For JOE to operate correctly, a number of other environment settings must be correct. The [...] The diff between joe.1.in from joe-2.9.8-pre1 downloaded from sourceforge is joined. I do not know how to use ^[ E so I didn't speak about it :-) -- Nicollet Xavier I2 Info EFREI Linux: http://www.linux.efrei.fr/ Le piratage tue le libre |
From: Xavier N. <nic...@ef...> - 2002-02-11 00:09:36
|
Well, I didn't find the compile option very "user friendly". That config trick should help: :def done msg,"done",rtn edit,"Compile buffer",rtn,filt,"make -s ", query,parserr,notmod,done ^[ c Compile It is nearly the same thing as before but the usual make -s is already written and the window can be closed without confirmation. Nevertheless, if you compile the same program several times, several compile windows will be opened. IMHO it would be better to have a unique window for compiling. Any idea on how to do this ? -- Nicollet Xavier I2 Info EFREI Linux: http://www.linux.efrei.fr/ Le piratage tue le libre |
From: Vitezslav S. <sa...@ma...> - 2002-02-07 08:20:37
|
Hi! > Thank you for the make -s tip > > > > Moreover, I didn't find where the man page deals with it. > > Maybe you could write about it and it to us ;-)) > > As I didn't know it well, I expected someone to explain it :) > But you're right, I'd better write a little text which could be inserted > into the man-page. > > BTW, is it planned to write some documentation with linux-doc or DocBook ? Marek Grac started writing some documentation (see docs/help-system.html) in plain HTML. I prefer to have some format (sgml, ...) from which we can generate all other formats (html, man, pdf, ps, ...) but I also want to have very small dependency on other not-so-standard tools to view joe documentation. Cheers Vita |
From: Matthias B. <mat...@wi...> - 2002-02-05 09:38:52
|
On Mon, 4 Feb 2002 14:42:41 +0100 "Vitezslav Samel" <sa...@ma...> wrote: > Hi! > > > > 1. It lacks bol ^[[H, bol ^[[1~, eol ^[[F, eol ^[[4~ entries. Older > > > joerc's had it, as well as current jpicorc/others have it, too. > > > This make Home/End unusable in xterm by default. > > > > This is probably a good idea, but it doesn't work for me with joe > > 2.8 (Mandrake 8.0) and Eterm. > > Does bol .kh and eol .kH should work ? > > Maybe it's time to have correct terminfo databases. > ^[[H, ^[[1~, ^[[F, ^[[4~ entries are only for those of you, who don't > have correct terminfo db. Nope. This is a terminal configuration issue. The terminfo database entry of ^[OH is correct for xterm when it has "Enable Application Cursor Keys" enabled. The ^[[H is only sent when it is disabled (and then those keys are not supposed to be interpreted). To enable this setting, either use the Ctrl-Middle-Click menu or put the following into your .Xresources ("Enable Application Keypad" should be on, too): XTerm.VT100.AppcursorDefault: true XTerm.VT100.AppkeypadDefault: true > (On my system I found another xterm terminfo definition named > xterm-new: try `TERM=xterm-new joe` and tell me if Home and End keys > work for you now. To Egmont: according to your address you have > slightly more power than me to convince large Linux distribution to > have xterm-new to be xterm as default.) To change the setting of TERM that xterm uses, put the following into .Xresources XTerm.TermName: xterm-xfree86 MSB -- I used to have an open mind but my brains kept falling out. |
From: Vitezslav S. <sa...@ma...> - 2002-02-07 08:39:36
|
> > > > 1. It lacks bol ^[[H, bol ^[[1~, eol ^[[F, eol ^[[4~ entries. Older > > > > joerc's had it, as well as current jpicorc/others have it, too. > > > > This make Home/End unusable in xterm by default. > > > > > > This is probably a good idea, but it doesn't work for me with joe > > > 2.8 (Mandrake 8.0) and Eterm. > > > Does bol .kh and eol .kH should work ? > > > > Maybe it's time to have correct terminfo databases. > > ^[[H, ^[[1~, ^[[F, ^[[4~ entries are only for those of you, who don't > > have correct terminfo db. > > Nope. This is a terminal configuration issue. The terminfo database entry > of ^[OH is correct for xterm when it has "Enable Application Cursor Keys" > enabled. The ^[[H is only sent when it is disabled (and then those keys > are not supposed to be interpreted). To enable this setting, either use ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This I wanted to hear ;-)). In ideal world we would have in rc-files only termcap / terminfo entries, but this is not possible in real world. So I'm inserting back those entries for now. Cheers, Vita |
From: Koblinger E. <eg...@su...> - 2002-02-05 10:35:23
|
> Maybe it's time to have correct terminfo databases. > ^[[H, ^[[1~, ^[[F, ^[[4~ entries are only for those of you, who don't have > correct terminfo db. If you want the Home and End keys set system-wide (for all > r insert) applications which uses terminfo) change khome and kend entries in > your terminfo DB. Meanwhile I should either put those entries back into joerc > or place some "BIG FAT WARNING" into README about those issues. Yes, it is time, but it must have some reason why we don't yet have it. And as I have no idea how these terminfo dbs look like, the easiest way is to patch joerc. Anyway, IMHO these kind of keybindings should be the same in all the five rc files. So either all or none of them should have "eol ^[[4~" and others. In the mean time I send a big fuck to the authors of Eterm. You launch it (numlock is off), then keypad generates "^[[A" and others. Press numlock twice, and then keypad generates completely different codes such as "^[Ox". > To Egmont: according to your address you have slightly more power than me to > convince large Linux distribution to have xterm-new to be xterm as default.) Slightly :-((( I've chosen to patch joerc, this is a much faster solution. Btw it's not yet decided whether we'll upgrade to 2.9.8pre1 or stay at 2.9.5 for the next SuSE distro, but I've been using 2.9.8pre1 for a while and had no problems with it. It seems that those wordwrap and paragraph-reformatting problems are gone forever... am I right? bye Egmont |
From: Vitezslav S. <sa...@ma...> - 2002-02-07 08:43:50
|
> Btw it's not yet decided whether we'll upgrade to 2.9.8pre1 or stay at > 2.9.5 for the next SuSE distro, but I've been using 2.9.8pre1 for a while > and had no problems with it. It seems that those wordwrap and > paragraph-reformatting problems are gone forever... am I right? Yes. Maybe I could release 2.9.8-pre2 - there is a fix for segmentation fault (moving rectangle block with -lightoff) in CVS - check out ChangeLog. Cheers Vita |
From: Mikhael G. <mi...@ho...> - 2002-01-31 22:53:45
|
On 31 Jan 2002 23:22:35 +0100, Koblinger Egmont wrote: > > 2. I generally hate if someone wants to force his personal preferences to > other people, but now this situation might be different. :) > > The topmost line has a "%t" item to display the current time. I really > doubt if anyone uses it, there's a command "date", there's a clock on > most people's desktop, and it's not the job of a text editor to display > the time. Furthermore, in multiple window mode you can see the current > time multiple times, wasting lots of space on the screen. > > Instead, displaying the percent where the cursor is, is really useful, > helps editing long texts, and this is something a text editor should > really do. > > So, if everyone agrees, I recommend replacing "%t" by "%p%%" in "-rmsg". Just FYI, I have both (time in bold %u and percentage), pretty useful. I don't care if the default string is changed, I don't use it anyway. :) -lmsg \i%k%*%R \b%n %M -rmsg \b%S +%r/%c %a%p%% \b%u\b Regards, Mikhael. |