[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

4502.0. "Keymaping on A500 ?" by DUCK::NONDEP () Sat Feb 09 1991 08:24

    
    
    Hello,
    
    I need some help once again,
    
    How do you change the keyboard definition. Setmap or keymap something !
    
    I can't get it to work. I read the A500 user manual and my WP manual
    but i must be missing something or the other.
    
    Thanks in advance, Patrick
T.RTitleUserPersonal
Name
DateLines
4502.1setmap GBARRODS::GOLDSTEINSteve G DTN: 847-5415Mon Feb 11 1991 04:426
    
    
    	You are right ... you use Setmap GB of USA1 USA2 etc 
    
    the file then looks for one of the files in the devs:keyboard
    directory...
4502.2Setmap=f for french keyboardDUCK::NONDEPMon Feb 11 1991 05:0214
    Steve,
    
    I've tried this. I have a physical french keyboard and have a program
    that uses the GB or US and can't seem to make it work.
    
    Do i need to re-load re-start the package (Prowrite V3.1.1 ) 
    once I have done the modification ?
    
    How do i check if it has worked, been stored ? 
    
    Does is stay there permanently ?
    
    Thanks in advance, Patrick
    
4502.3ULTRA::KINDELBill Kindel @ LTN1Mon Feb 11 1991 09:0622
    Re .2:
    
>   Do i need to re-load re-start the package (Prowrite V3.1.1 ) 
>   once I have done the modification ?
    
    Any program that is sensitive to which keyboard you're using will need
    to be started AFTER you've changed you keymappings.  (They have no way
    to tell that things have changed.)  I use ProWrite 3.0 with my U.S.
    keyboard and I've noticed that ProWrite has its own mappings for
    international characters (in particular, Prowrite defines "dead keys"
    on the home row for the addition diacritical marks over vowels) that
    don't match the basic Amiga mappings.  (Actually this issue is more
    complex than that -- I don't know if ProWrite does its mapping from the
    invariant key NUMBER or the mapped key VALUE.)
    
>   How do i check if it has worked, been stored ?
>    
>   Does is stay there permanently ?
    
    I think you need to put the keyboard mapping into s/startup-sequence so
    it will be performed each time you boot your system.
                                                  
4502.4MQOFS::DESROSIERSLets procrastinate....tomorrowMon Feb 11 1991 11:468
    Some programs accept the keymaps selected (like Word Perfect) and some
    just revert back to the basic USA keymap (like DPaint) and some make up
    their own keymaps (like VT200, VLT).  It WOULD be nice if they all
    responded the same to keymaps, especially for people who write in a
    language OTHER than english.
    
    Jean
    
4502.5Yep have a go at re-mapping the worldDUCK::NONDEPMon Feb 11 1991 12:406
    Well,
    
    I guess i'll have a go at .3 tonight and see how i can acess the
    startup sequence to make the change permanent.
    
    Thanks, Patrick
4502.6It works but not permanently !DUCK::NONDEPTue Feb 12 1991 06:3318
    
    Hello,
    
    Well yesterday I managed to map Prowrite. I open the system drawer,
    bring up the cli shell, type setmap f, close cli, and off i go, this
    must be done everytime i access prowrite
    
    I can either open the cli after my document or before the changes takes
    places as and when.
    
    I don't know how to edit the s:startup-sequence to make my changes
    permanent. My user manual is too/not detailed enough for me.
    
    
    Cheers, Patrick 
    
    
    
4502.7Simple editingULTRA::KINDELBill Kindel @ LTN1Tue Feb 12 1991 09:5227
    Re .6:
    
>   I don't know how to edit the s:startup-sequence to make my changes
>   permanent. My user manual is too/not detailed enough for me.
    
    While you COULD do it from ProWrite, I'd suggest using the simple ED
    editor that is provided with the system and documented along with the
    other CLI commands.  In essence, here's what you'll do.  I'll mark CLI
    and ED inputs with CLI> and ED>, respectively.  Comments are in braces.
    
    1.	Open a CLI/Shell window.
    2.	CLI>	cd sys:s
    3.	CLI>	copy startup-sequence startup-sequence.backup
    4.	CLI>	ed startup-sequence
    		{ The file will be displayed in a full screen. }
    5.	ED>	{ Use the cursor keys to get down near the end,
    		  but before the workbench is started. }
    6.	ED>	{ Enter a carriage return to open an empty line. }
    7.	ED>	setmap f ; Set French keyboard mapping.
    		{ Everything following a ; will be considered a comment. }
    		{ If you end up with an extra blank line, you can delete
    		  it by placing the cursor on it and typing ^B (Control-B). }
    8.	ED>	<ESC> x		{ Escape key, then X to 'eXit'. }
    		{ The file will be rewritten to disk. }
    		{ If you DON'T want to save your changes, type <ESC> q
    		  ( Escape key, then Q ) to 'Quit'. }
    9.	Reboot.	{ Control+L_Amiga+R_Amiga }
4502.8FWIWCRISTA::CAPRICCIOBlind as a cave shrimpTue Feb 12 1991 12:098
�   3.	CLI>	copy startup-sequence startup-sequence.backup

    While this step is *always* a good idea, one nice thing ED does for you
    is when you "X" (exit) from ED, it will copy the original file to
    "sys:t/ed-backup". Not bad for no-frills screen editor, eh?  However,
    the next time you invoke ED and exit, the contents are overwritten...

    Pete