Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.sys.mac.system Subject: Re: MacsBug 6.1 & foreign keyboard Message-ID: Date: 19 Dec 90 00:07:45 GMT References: <1990Dec16.215824.24325@ida.liu.se> <2553.276e53dc@waikato.ac.nz> Organization: University of Karlsruhe, FRG Lines: 24 In comp.sys.mac.system, article <2553.276e53dc@waikato.ac.nz>, ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) writes: < Try pasting the US KCHR resource (or whichever you want to use) into < MacsBug's "Debugger Prefs" file. This should stop it using your < system's KCHR altogether. Yes, but that also means that everything else is where it's supposed to be on a US keyboard. This is *frustrating*. A better idea is to use Command-D as an alias for Command-:. Newer versions of Macsbug actually document that in the help text. (And, don't forget changing to the heap where the symbols in question are supposed to be in, if that heap isn't the current application's heap. HX @applZone (2aa) changes to the current application's heap permanently if you are running under Mutlifinder; that's important if the application in question uses silly things like completion routines or VBLs.) < < I think this is documented in the MacsBug manual somewhere. < What's a "manual"? ;-) -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/