Joe, Options: *--silent * Start without a default window *--preload * Preload for later use *--profile <profile>* Profile to open *--profiles * List available profiles *--mimetype <mimetype>* Mimetype to use for this URL (e.g. text/html or inode/directory) *--select * For URLs that point to files, opens the directory and selects the file, instead of opening the actual file Generic options: *--help * Show help about options *--help-qt * Show Qt specific options *--help-kde * Show KDE specific options *--help-all * Show all options *--author * Show author information *-v, --version * Show version information *--license * Show license information KDE options: *--caption <caption>* Use 'caption' as name in the titlebar *--icon <icon>* Use 'icon' as the application icon *--miniicon <icon>* Use 'icon' as the icon in the titlebar *--config <filename>* Use alternative configuration file *--dcopserver <server>* Use the DCOP Server specified by 'server' *--nocrashhandler * Disable crash handler, to get core dumps *--waitforwm * Waits for a WM_NET compatible windowmanager *--style <style>* sets the application GUI style *--geometry <geometry>* sets the client geometry of the main widget Qt options: *--display <displayname>* Use the X-server display 'displayname' *--session <sessionId>* Restore the application for the given 'sessionId' *--cmap * Causes the application to install a private color map on an 8-bit display *--ncols <count>* Limits the number of colors allocated in the color cube on an 8-bit display, if the application is using the QApplication::ManyColor color specification *--nograb * tells Qt to never grab the mouse or the keyboard *--dograb * running under a debugger can cause an implicit -nograb, use -dograb to override *--sync * switches to synchronous mode for debugging *--fn, --font <fontname>* defines the application font *--bg, --background <color>* sets the default background color and an application palette (light and dark shades are calculated) *--fg, --foreground <color>* sets the default foreground color *--btn, --button <color>* sets the default button color *--name <name>* sets the application name *--title <title>* sets the application title (caption) *--visual TrueColor* forces the application to use a TrueColor visual on an 8-bit display *--inputstyle <inputstyle>* sets XIM (X Input Method) input style. Possible values are onthespot, overthespot, offthespot and root *--im <XIM server>* set XIM server *--noxim * disable XIM *--reverse * mirrors the whole layout of widgets
On Sat, Jun 9, 2012 at 10:15 PM, <[email protected]> wrote: > > Had not heard of --silent before, but I did try it now > and got the same result as before. > Let's see: # konqueror --silent lb.htm Should mute that debug log noise? Also, you want to bypass running the startup from console to open konqueror for that htm file? You create a KDE shortcut to konqueror in your menu and set the htm file to open in a custom profile: You may also open it to your desired profile from the command line with *konqueror --profile filemanagement* or *konqueror --profile webbrowsing*. How do you know what the profile names are? Run $ * konqueror --profiles* filemanagement webbrowsing Check out "*man konqueror*"** Now you know which command to use to create a menu icon. Open the KDE menu editor by right-clicking on the blue K, or run *kmenuedit* from a command line. Click New Item. You need only three things: a name that you make up, the correct command, and a nice icon which you can find by clicking on the icon box. Customizing Profiles You may also easily customize your profiles. For example, I want Konqueror the file manager to always open at the same directory. So I open it to that directory, then do "Settings --> Save View Profile File Management". Checking "Save URLs in view profile" makes sure it will always open to my chosen directory. You can customize Konqueror to your heart's content and then save it in a profile, and you can even create customized profiles under different names for all occasions. This works for both Web and file manager profiles. http://www.datamation.com/osrc/article.php/3796771/Making-KDEs-Konqueror-Obey-You.htm > Hi Joe, > > Did you try to send it the silent flag? > > $ konqueror lb.htm --silent > > > On Sat, Jun 9, 2012 at 2:51 PM, <[email protected]> wrote: > >> >> When I do (from the command line): firefox lb.htm ... it works >> perfectly. >> No complaints. >> When I do (from the command line): konqueror lb.htm ... it works fine, >> >> but I get the series of complaints listed below. >> >> Any idea how to stop those complaint messages? >> >> Also, how can I execute either a firefox or konqueror activation of a >> named 'htm' file from the command line without the terminal window >> having >> to stay open? >> >> $ konqueror lb.htm >> konqueror(9218)/kdeui (kdelibs): Attempt to use QAction "konqbrowser" >> with >> KXMLGUIFactory! >> konqueror(9218)/kdeui (kdelibs): Attempt to use QAction "firefox" with >> KXMLGUIFactory! >> konqueror(9218)/kdeui (kdelibs): Attempt to use QAction "" with >> KXMLGUIFactory! >> QPainter::begin: Widget painting can only begin as a result of a >> paintEvent >> QPainter::translate: Painter not active >> QPainter::setClipRect: Painter not active >> QPainter::hasClipping: Painter not active >> QPainter::setPen: Painter not active >> QPainter::setBrush: Painter not active >> QPainter::hasClipping: Painter not active >> QPainter::setPen: Painter not active >> QPainter::setBrush: Painter not active >> QPainter::hasClipping: Painter not active >> QPainter::setPen: Painter not active >> QPainter::setBrush: Painter not active >> QPainter::hasClipping: Painter not active >> QPainter::setPen: Painter not active >> QPainter::setBrush: Painter not active >> >
--------------------------------------------------- PLUG-discuss mailing list - [email protected] To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
