Re: Key assignment

[Ivan B. <lu...@ad...>]

	Hello.
	Since we are there, I think it would be better if all the configuration
of the editor was in text format, text configuration files are the most
flexible of all configuration files.
	It would be nice (if the configuration changes from binary to text) to
be able to include configuration files from one file to other, something
like the #include "" in CPP, in this way the editor can come with
standard configuration files and then the user can include them from
their own main configuration file or just copy&paste and change some
things.
	The problem with text files, is that the editor would have to try hard
to not screw up the user hand-made changes.
	On the other hand, if the editor is fully configurable via SLisp
commands, then the configuration files could be simple SLisp files
specifying things and doing some actions, that would give a lot of
flexibility, but how the editor can change the configuration files made
by the user?
	Though, all that seems very complex, so as Thiago suggests: the
.keybinds.dat should be a text file.
	Goodbye.

P.s.: just a suggestion and see if it is possible...


"Thiago F.G. Albuquerque" wrote:
> 
> Hi,
> 
> I have some things to say about the key assignment in SETEDIT.
> 
> First of all, I think ".keybinds.dat" should be a text file.
> 
> I change most of the default key assignments. For me it is easier/faster to edit a file than to
> reassign key by key using the GUI. And when I get a new version of SETEDIT I don't have to do it
> all again; I can just copy the file. Yes, right, I can do that with the binary file too. But if
> the file format changes from one version to the other (like the pmacros file changed, for
> instance), it is possible for me to peek at the files, see what has changed and make the
> necessary modifications.
> 
> The list of key assignments doesn't show the keys assigned by the menues. This can be pretty
> annoying; I reassigned f9 to "make", but it didn't take effect because some menu assigned it to
> SDG. I think all key assignments should be in the same place.
> 
> One possible solution to this: menubind.smn doesn't assign keys. At most, it specifies the name
> of the key that shows in the menu, but the actual key assignment is in keybinds.dat. Drawback:
> the information in the menus can get "old" (in the sense of not corresponding to the reality
> anymore). If you reassign a key related to some menu, you have to edit menubind.smn and change
> the key name. Not a very big problem, though.
> 
> Another (better) idea:
> 
> New file: ~/seteditrc -> user-specific macros and key assignments. Loaded at startup.
> New sLisp command: (bind keys command/macro)
> 
> e.g.:
>     (bind "^L" cmcOpenFile) ; assigns CTRL-L to cmcOpenFile
>     (bind "#^M"  my_macro)  ; CTRL-SHIFT-M to my_macro
> 
> where
> ^ == CTRL
> # == SHIFT
> @ == ALT
> 
> This way you can define your macros and assign them to a key in the same file, like in Emacs.
> 
> This solution also addresses another issue: the lack of user-specific macros. The macros file is
> system-wide and you can edit it only if root lets you do so.
> 
> What do you think, SET?
> 
> Thiago
> 
> _______________________________________________
> Setedit-users mailing list
> Set...@li...
> http://lists.sourceforge.net/lists/listinfo/setedit-users

-- 
Ivan Baldo:
lu...@ad... - http://go.to/ibaldo - ICQ 10215364
Phone: (598) (2) 613 3223.
Caldas 1781, 11400 Malvin, Montevideo, Uruguay, South America.

(If you have problems with the previous addresses, try this ones:
ib...@us..., http://members.xoom.com/baldo.1).