[MacPorts] #38544: KDE - Kate Launch
#38544: KDE - Kate Launch ----------------------------+-------------------------------- Reporter: rob.edgerley@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ----------------------------+-------------------------------- Hi all, After downloading kate, I was expecting to be able to launch the application by simply writing 'kate' into the terminal. However, this turns out not to be the case. Ive made sure to do all of the following: sudo chown -R $USER ~/Library/Preferences/KDE sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus- system.plist launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist but alas, no joy. Any ideas here? Furthermore: as a workaround I made an alias in my .bash_profile as follows: alias kate='open -a kate' which kind of works, but it's quite odd. If I then type into the terminal.... kate <file_i_want_to_open_and_edit> ....then kate launches, but not with the file I specified. Instead, an untitled blank file. Any suggestions how I might go about solving this problem will be greatly appreciated. - Rob -- Ticket URL: <https://trac.macports.org/ticket/38544> MacPorts <http://www.macports.org/> Ports system for OS X
#38544: Kate cannot be launched from the command line -----------------------------+--------------------- Reporter: rob.edgerley@… | Owner: nicos@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: kate | -----------------------------+--------------------- Changes (by jmr@…): * owner: macports-tickets@… => nicos@… * type: request => defect * port: => kate Comment: Please remember to fill in the Port field and Cc the maintainer. -- Ticket URL: <https://trac.macports.org/ticket/38544#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#38544: Kate cannot be launched from the command line -----------------------------+--------------------- Reporter: rob.edgerley@… | Owner: nicos@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: kate | -----------------------------+--------------------- Comment (by nicos@…): KDE ports usually install binaries as application bundles in the macports application directory, so there should be an application bundle in /Applications/MacPorts/KDE4/ (if you use default settings) that can be double-clicked on. [[BR]] So, if there is really a need to launch kate through the Terminal instead of through the Finder, running {{{ /Applications/MacPorts/KDE4/kate.app/Contents/MacOS/kate }}} should work. Additionally, I think the command {{{ sudo chown -R $USER ~/Library/Preferences/KDE }}} is not needed. You can also refer to [wiki:KDE Installing KDE] for details. Does this answer the question, or is there an issue I am missing ? -- Ticket URL: <https://trac.macports.org/ticket/38544#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#38544: Kate cannot be launched from the command line -----------------------------+--------------------- Reporter: rob.edgerley@… | Owner: nicos@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: kate | -----------------------------+--------------------- Comment (by rob.edgerley@…): Hi, thanks for the reply! No, this doesn't really help. I don't see the advantage of launching kate via the terminal using: {{{ /Applications/MacPorts/KDE4/kate.app/Contents/MacOS/kate }}} over the method I have already noted. i.e. {{{ alias kate='open -a kate' }}} they both behave in the same, and both do not open the file I have specified to open. Your suggestion also seems to launch an additional terminal window. I simply want to launch kate using the terminal, as I already use it for most things. If it's not possible, it's ok, i'll just continue to use nedit. Thanks for taking the time to reply though! -- Ticket URL: <https://trac.macports.org/ticket/38544#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38544: Kate cannot be launched from the command line -----------------------------+--------------------- Reporter: rob.edgerley@… | Owner: nicos@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: kate | -----------------------------+--------------------- Comment (by rob.edgerley@…): Hi nicos@macports.org, Sorry and sorry again. I was in a rush and I didn't test this correctly. Indeed, this does exactly what I want. Thanks! -- Ticket URL: <https://trac.macports.org/ticket/38544#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#38544: Kate cannot be launched from the command line -----------------------------+--------------------- Reporter: rob.edgerley@… | Owner: nicos@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: worksforme | Keywords: Port: kate | -----------------------------+--------------------- Changes (by nicos@…): * status: new => closed * resolution: => worksforme Comment: Good it works, I was just answering. I put it down here for the sake of completeness, or if someone else runs into this. Adding the file as an argument should open it. So by putting {{{ alias kate='/Applications/MacPorts/KDE4/kate.app/Contents/MacOS/kate' }}} in the .profile file for the case of default MacPorts paths, it should be possible to run {{{ kate <file> }}} to open it through the Terminal. -- Ticket URL: <https://trac.macports.org/ticket/38544#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#38544: Kate cannot be launched from the command line -----------------------------+--------------------- Reporter: rob.edgerley@… | Owner: nicos@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: worksforme | Keywords: Port: kate | -----------------------------+--------------------- Comment (by rob.edgerley@…): Hi again, Indeed that works.The way I actually solved it, rather than adding yet another alias to the .profile file, was to add a logical link to {{{ /Applications/MacPorts/KDE4/kate.app/Contents/MacOS/kate }}} in the following location {{{ /opt/local/bin }}} I did this by navigating to: {{{ /opt/local/etc }}} and typing "as root", the following command: {{{ ln -s /Applications/MacPorts/KDE4/kate.app/Contents/MacOS/kate kate }}} Now simply typing: {{{ kate <file> & }}} does the trick. Hope this helps someone out there! -- Ticket URL: <https://trac.macports.org/ticket/38544#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts