One problem with TextEdit is that it can introduce line endings which 
make Unix script files dysfunctional.  I don't think that this is the 
case here, though.

Can you post the contents of your .xinitrc file?

Alexander K. Hansen wrote:
> Define "the file":  the system's xinitrc or ~/.xinitrc ?  If the 
> latter it -should- belong to you and not be locked.  If you edited the 
> system's xinitrc file, but you also have a ~/.xinitrc, then the former 
> gets ignored completely in favor of the latter.
>
> I have no idea what X11 Starter is or how it works.
>
> Chris Lord wrote:
>> Alex,
>>
>> Gave up trying to edit the file in pico and figured out a way to 
>> change the file permissions using Get Info, added the lines at the 
>> end of the file and saved them using Text Edit (which at least does 
>> what you tell it to!), then locked the file again. However KDE did 
>> not automatically launch when I launched X11, and when I used X11 
>> Starter to launch KDE, I still have the same problem with the mouse 
>> not interacting with the window buttons.
>>
>> Chris Lord
>>
>>
>> On 17 Jul 2007, at 14:24, Alexander K. Hansen wrote:
>>
>>     You -don't- want to launch it from a terminal after X is going
>>     (especially this outdated version). Put the following lines in
>>     your ~/.xinitrc file:
>>
>>
>>     export KDEWM=kwin
>>     source /sw/bin/init.sh
>>     /sw/bin/startkde >/tmp/kde.log 2>&1
>>
>>     Then start X and KDE will start automatically.
>>
>> ___________________________________
>>
>


-- 
Alexander K. Hansen
Fink User Liaison/Documenter
akh AT finkproject DOT org


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to