Bug 212462 - geometry command line option is ignored
Summary: geometry command line option is ignored
Status: RESOLVED DUPLICATE of bug 147094
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-31 03:21 UTC by furue
Modified: 2010-01-25 18:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description furue 2009-10-31 03:21:44 UTC
Version:            (using KDE 4.3.1)
Installed from:    Debian testing/unstable Packages

I think that the ability to set the size of the konsole window from the command line as

   $ konsole --geomtry 80x24 # in terms of lines and columns
  or   --geometry 300x200 # in terms of pixels

is necessary.  Consider, for example, a situation where you use konsole in a .desktop file as

   Exec=/usr/bin/konsole -e cli_command --geometry 80x24

It is annoying that the size of the window is affected by the "current" setting.

The initial messge of Bug 152385 mentions this issue, but the subsequent responses ignored it and focused on other ones.  I want the --geometry issue to be separate.

In passing, it is strange that konsole does not issue an error message when either --geometry or -geometry is specified.
Comment 1 furue 2009-10-31 03:35:34 UTC
I mentioned "Bug 152385", but I meant Bug 196397 .  I'm sorry for the mistake.

By the way, that was the only relevant (as far as I could tell from the titles of the bugs) report I found in the "Check for Duplicate Bug Reports" page of the KDE Bug Report Wizard.
Comment 2 Semo 2009-11-04 22:31:54 UTC
Same for me. Cmdline option --geometry for konsole is silently ignored and size of just created window is determined I don't know how as well as placement on the desktop.
Comment 3 Jonathan Marten 2010-01-25 18:53:19 UTC

*** This bug has been marked as a duplicate of bug 147094 ***