Bug 137996 - Ability to change font sizes when reading messages
Summary: Ability to change font sizes when reading messages
Status: RESOLVED DUPLICATE of bug 131449
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.9.5
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-28 05:08 UTC by johnelliottmartin
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description johnelliottmartin 2006-11-28 05:08:08 UTC 
Version:           1.9.5 (using KDE 3.5.5 "release 39" , openSUSE 10.2)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.2-23-default

I would love it if it was possible to press ctrl + + and ctrl + - to change the font's display size in kmail as you can in konqueror and other apps. 

I don't know if this is something anyone else is interested in, but I love being able to scale the fonts way up and lean back to read an email or a website (I don't need my glasses then!).
Comment 1 Philip Rodrigues 2006-11-28 09:32:29 UTC 
Seems you're not the only one to want this, though I don't really understand why not just change the font size in settings->configure kmail if it's too small

*** This bug has been marked as a duplicate of 131449 ***
Comment 2 johnelliottmartin 2006-11-28 12:39:12 UTC 
The reason is that I don't want to change the default font size because most of the time small fonts are fine. However, when I receive a large multipage email I like to bump up the font size and lean back and read. 

Right now my email is through gmail, so I when I get a big message I just open up Konqueror and ctrl++ it to my liking, but it would be nice to be able to do this without leaving kmail.
Comment 3 Philip Rodrigues 2006-11-29 20:27:01 UTC 
Thanks for explaining the use case, John. Could you add that as a comment to bug 131449 as well?