From: David P. <ele...@gm...> - 2005-03-25 00:14:38
Attachments:
mouse-shell.patch
|
The new mouse support in JOE 3.2 is great. However, there is a bug: the "shell" action does not de-initialize the mouse. In the course of fixing this, I cleaned up the mouse support a bit. I moved the mouse terminal code to two functions in mouse.c: mouseopen and mouseclose. nescape calls mouseclose, nreturn calls mouseopen, nopen calls mouseopen and nclose calls mouseclose. Questionable change: the middle of nopen used to de-initialize the mouse. Why did it do this? Is my fix / cleanup correct? It works fine for me in PuTTY, but I haven't tested it anywhere else. I can commit these changes if they are confirmed correct. Thanks to Joseph Allen and everyone else for the best UNIX text editor! -- David Phillips <da...@ac...> http://david.acz.org/ |
From: Mikhael G. <mi...@ho...> - 2005-03-25 02:45:56
|
On 24 Mar 2005 18:14:28 -0600, David Phillips wrote: > > Thanks to Joseph Allen and everyone else for the best UNIX text editor! Here is my "me too". :) Many thanks for continuing to develop joe! On the topic. I really dislike to have mouse to be managed by joe, :) as well as some other features like autoindent, locks, home instead of bol, that all seem to be the default now. But I tried not to disable them, and to try to learn them first. I am not sure enabling autoindent by default is good, and there is no easy way to disable it without commenting many lines. One serious problem with autoindent is that pasting multi-line source code shifts every new line to the right, the result is screwy. But at least everything may be disabled and configured like I want. Thank you again. Great work. Regards, Mikhael. |
From: Jacob E. <ja...@lu...> - 2005-03-25 23:28:16
|
On Fri 25 Mar 02005 at 02:45:22AM +0000, Mikhael Goikhman wrote: > On 24 Mar 2005 18:14:28 -0600, David Phillips wrote: > > > > Thanks to Joseph Allen and everyone else for the best UNIX text editor! > > Here is my "me too". :) Many thanks for continuing to develop joe! > > On the topic. I really dislike to have mouse to be managed by joe, :) as > well as some other features like autoindent, locks, home instead of bol, > that all seem to be the default now. But I tried not to disable them, and > to try to learn them first. I am not sure enabling autoindent by default > is good, and there is no easy way to disable it without commenting many > lines. One serious problem with autoindent is that pasting multi-line > source code shifts every new line to the right, the result is screwy. > This has been my habit for literally a decade: ^T^I^T^W *paste* T^I^T^W But I can see where you're coming from. I would, more than anything else, like to see a way to have real time on-screen-only word wrap that doesn't get saved with the file. > But at least everything may be disabled and configured like I want. > Thank you again. Great work. > Yes, great work! -- Jacob Elder |
From: Joseph H A. <jh...@th...> - 2005-03-25 17:22:46
|
>On 24 Mar 2005 18:14:28 -0600, David Phillips wrote: >On the topic. I really dislike to have mouse to be managed by joe, :) as >well as some other features like autoindent, locks, home instead of bol, >that all seem to be the default now. But I tried not to disable them, and >to try to learn them first. I am not sure enabling autoindent by default >is good, and there is no easy way to disable it without commenting many >lines. One serious problem with autoindent is that pasting multi-line >source code shifts every new line to the right, the result is screwy. Ok, so I've just sent mail to Thomas Dicky, who I think is the maintainer of XTerm. I've asked if he is willing to accept an xterm patch which will improve the autoindent (and `) bug, as well as allow for X cut and paste, when xterm mouse mode is enabled. If he is willing to take a patch, I'll do it, but you have to upgrade your xterms :-) As far as the other things, realize that I have to compromize between exact compatibility and new features. In fact I got sick of the Ctrl-SPACE not being insert space in overtype mode (I tried making it a block selection method in JOE-3.1), so I took it out for JOE-3.2. What's wrong with the locks? Too much clutter, or editing files in directories with no write permission? Maybe locks should optionally go in the backpath directory. >But at least everything may be disabled and configured like I want. >Thank you again. Great work. > >Regards, >Mikhael. Joe |
From: David P. <ele...@gm...> - 2005-03-25 18:20:30
|
On Fri, 25 Mar 2005 12:03:02 -0500 (EST), Joseph H Allen <jh...@th...> wrote: > I've asked if he is willing to accept an xterm patch which will > improve the autoindent (and `) bug How about a paste mode that is easy enable and disable. It would temporarily disable autoindent and ` (or perhaps, more generally, cause any regular key to act normally). I actually started working on a patch for this a while ago, but at this point it probably needs to be restarted. -- David Phillips <da...@ac...> http://david.acz.org/ |
From: Brian C. <B.C...@po...> - 2005-03-26 11:31:04
|
On Fri, Mar 25, 2005 at 12:03:02PM -0500, Joseph H Allen wrote: > What's wrong with the locks? Because they're not needed? I understand they there just to benefit emacs users, which has its own locking convention? I *loathe* emacs. Other people love it - and would never look at joe. The overlap, that is people who use both emacs and joe, is probably small; so I think they should have to explicitly enable emacs-locking if they want it. Regards, Brian. |
From: Joseph H A. <jh...@th...> - 2005-03-26 15:25:20
|
Brian Candler <B.C...@po...> wrote: >On Fri, Mar 25, 2005 at 12:03:02PM -0500, Joseph H Allen wrote: >> What's wrong with the locks? >Because they're not needed? I understand they there just to benefit emac= s >users, which has its own locking convention? I've had JOE users ask for them:=A0 They really have nothing to do with e= macs, except that I implemented them in the same way. The idea is that if you have lots of windows on the screen, with a bunch JOEs suspended, it is ea= sy to get confused and modify the same file twice. With the locks, JOE warn= s you that it happened as soon as you start editing. The emacs way, i.e., with the locks as softlinks, is nice compared to using UNIX OS advisory locks: flock(), fcntl() or lockf(), because it's more portable. JED implements the locks the same way, too. VIM doesn't have locks yet. = If all the common editors use the same locks, a bunch of people could safely edit files in the same directory. >I *loathe* emacs. Other people love it - and would never look at joe. Th= e >overlap, that is people who use both emacs and joe, is probably small; s= o I >think they should have to explicitly enable emacs-locking if they want i= t. Well it's weird:=A0I can't stand the feel of emacs, and it's difficult to= grok the entire editor (there's no single manual to read, instead you are forc= ed to learn it incrementally). Plus I don't want to read news in my editor = :-) Also many things are clunky, like the highlighter and the hex editor. On the other hand, a lot of things are nice. They've thought a lot of things through properly, I envy EDIFF (wish it was stand alone tool), and LISP is very powerful (if difficult to type). >Regards, >Brian. Joe |
From: Matthew M. <ma...@ma...> - 2005-03-26 17:14:57
|
On Sat, Mar 26, 2005 at 09:18:07AM -0500, Joseph H Allen wrote: > JED implements the locks the same way, too. VIM doesn't have locks yet. Vim uses a ".filename.swp" thing, though, which has the same effect. -- Matthew Miller ma...@ma... <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> |
From: Joseph H A. <jh...@th...> - 2005-03-25 19:08:55
|
OK, I started looking at the xterm source code: If you compile it with "#define OPT_READLINE 1" in ptyx.h, and you send it the new magic code: ^ [ ? 2004 h, it then brackets pastes like this: ^[ [ 200 ~ <paste-text> ~[ [ 201 ~ I don't know why xterm doesn't have OPT_READLINE enabled by default. >From jhallen Fri Mar 25 12:03:02 2005 >To: joe...@li..., Mikhael Goikhman <mi...@ho...> >Subject: Re: [joe] Patch: Fix for mouse support >References: <853...@ma...> >Status: O > > >>On 24 Mar 2005 18:14:28 -0600, David Phillips wrote: > >>On the topic. I really dislike to have mouse to be managed by joe, :) as >>well as some other features like autoindent, locks, home instead of bol, >>that all seem to be the default now. But I tried not to disable them, and >>to try to learn them first. I am not sure enabling autoindent by default >>is good, and there is no easy way to disable it without commenting many >>lines. One serious problem with autoindent is that pasting multi-line >>source code shifts every new line to the right, the result is screwy. > >Ok, so I've just sent mail to Thomas Dicky, who I think is the maintainer of >XTerm. I've asked if he is willing to accept an xterm patch which will >improve the autoindent (and `) bug, as well as allow for X cut and paste, >when xterm mouse mode is enabled. If he is willing to take a patch, I'll do >it, but you have to upgrade your xterms :-) > >As far as the other things, realize that I have to compromize between exact >compatibility and new features. In fact I got sick of the Ctrl-SPACE not >being insert space in overtype mode (I tried making it a block selection >method in JOE-3.1), so I took it out for JOE-3.2. > >What's wrong with the locks? Too much clutter, or editing files in >directories with no write permission? Maybe locks should optionally go in >the backpath directory. > >>But at least everything may be disabled and configured like I want. >>Thank you again. Great work. >> >>Regards, >>Mikhael. > >Joe > Joe |
From: Mikhael G. <mi...@ho...> - 2005-03-26 18:25:13
|
On 25 Mar 2005 12:03:02 -0500, Joseph H Allen wrote: > > Ok, so I've just sent mail to Thomas Dicky, who I think is the > maintainer of XTerm. I've asked if he is willing to accept an xterm > patch which will improve the autoindent (and `) bug, as well as allow > for X cut and paste, when xterm mouse mode is enabled. If he is > willing to take a patch, I'll do it, but you have to upgrade your > xterms :-) Nice. Still I can't see myself using autowrap or autoindent for source files (autowrap is nice for email messages). This is a personal habit, I guess. My coding style is exactly one Tab per one identation level, so pressing one Tab key and one Backspace is all that is needed, I don't want the editor to help me here. :) Others may have their own habits. > As far as the other things, realize that I have to compromize between exact > compatibility and new features. Sure. Besides, as the main developer you have the last word. > In fact I got sick of the Ctrl-SPACE not being insert space in overtype > mode (I tried making it a block selection method in JOE-3.1), so I took > it out for JOE-3.2. It is your choice. Personally, I configured Shift-arrows to select text. > What's wrong with the locks? Too much clutter, or editing files in > directories with no write permission? Maybe locks should optionally go in > the backpath directory. I guess it is the same reason why I disable backup files. I don't want my file systems to be filled with unrelevent files. It is enough that there are lots of DEADJOE files already (I may leave joe open for several days and it is eventually killed), but at least these may be very useful. :) One serious problem for me (inherent more to backups than to lock) is that sometimes you may edit a huge file on an almost full file system. I would just end up to always removing backups and this is very annoying. Another problem is that I often run joe to view a file and still want to occasionally use it as a sandbox (to urgently type some info that I got by phone, or just to test some new ideas that I know will be undo'ne or thrown away). The read-only files have the same problem, but at least this happens rarely and there is a key to enable full editing. And finally, just noticed, my handy short shell alias to "joe /dev/null" (sandbox) does not work well anymore. Locks are something I never want. But others may like them possibly, I don't know. > >But at least everything may be disabled and configured like I want. > >Thank you again. Great work. Regards, Mikhael. |
From: Matthew M. <ma...@ma...> - 2005-03-26 18:30:10
|
On Sat, Mar 26, 2005 at 06:24:41PM +0000, Mikhael Goikhman wrote: > > In fact I got sick of the Ctrl-SPACE not being insert space in overtype > > mode (I tried making it a block selection method in JOE-3.1), so I took > > it out for JOE-3.2. > It is your choice. Personally, I configured Shift-arrows to select text. FWIW, I *hated* the block selection ctrl-space -- for some reason, I keep hitting it accidentally. -- Matthew Miller ma...@ma... <http://www.mattdm.org/> Boston University Linux ------> <http://linux.bu.edu/> |
From: Reuben D. B. <tec...@vo...> - 2005-03-28 13:09:17
|
On Saturday 26 March 2005 13:30, Matthew Miller wrote: > On Sat, Mar 26, 2005 at 06:24:41PM +0000, Mikhael Goikhman wrote: > > > In fact I got sick of the Ctrl-SPACE not being insert space in overtype > > > mode (I tried making it a block selection method in JOE-3.1), so I took > > > it out for JOE-3.2. > > > > It is your choice. Personally, I configured Shift-arrows to select text. > > FWIW, I *hated* the block selection ctrl-space -- for some reason, I keep > hitting it accidentally. hm.. I actually got quite used to it that now it's so ingrained in my brain I never use ^KB ^KK anymore to select text. Could this be in options ? Furthermore, there has been many new features in the editor, I can barely keep up with what's new, what's the default behavior, etc. Is there a list of all features together with the default behavior and shortcut keys or something like that ? Then for every new features / new default behavior in the new version, someone could just edit that list. I can volunteer to help with that, for example. Imagine that this is something to read for a new user coming in to use Joe. For example, I didn't even know about CTRL-g as the key to jump to the matching bracket until just very recently from the list. And from me too, thank you for this great editor. Thanks RDB -- Reuben D. Budiardja Dept. Physics and Astronomy University of Tennessee, Knoxville, TN -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT/M/MU/P/S d-(++) s: a-- C++(+++) UL++++ P-- L+++>++++ E- W+++ N+ o? K- w--- !O M- V? !PS !PE Y PGP- t+ 5 X R- tv+ b++>+++ DI D(+) G e++>++++ h+(*) r++ y->++++ ------END GEEK CODE BLOCK------ |
From: Moritz B. <bar...@gm...> - 2005-03-28 17:06:10
|
Hi list, On Mon, Mar 28, 2005 at 08:09:11 -0500, Reuben D. Budiardja wrote: > hm.. I actually got quite used to it that now it's so ingrained in my > brain I never use ^KB ^KK anymore to select text. Could this be in > options ? Same here. Ever since it was introduced, I've very much learned to love it. ^KB ^KK doesn't highlight running along with the cursor. It is already an option though. :-) Apart from that you still have some mechanisms such as Ctrl-arrow (?), you just have to change toggle_marking ^@ Ctrl-space block selection method insc ^@ Ctrl-space used to insert a space to toggle_marking ^@ Ctrl-space block selection method insc ^@ Ctrl-space used to insert a space in your joerc. All this just "as far as I can see", I haven't tried but just had a look at the most recent joerc. > For example, I didn't even know about CTRL-g as the key to jump to > the matching bracket until just very recently from the list. Same here. But have a look NEWS, there's a lot in there, it's probably worth a read. > And from me too, thank you for this great editor. <AOL>Me too.</AOL> :-) Moritz |