public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: heat codes
Date: Fri, 13 Mar 2015 06:31:45 -0500	[thread overview]
Message-ID: <5502CAA1.6030102@gmail.com> (raw)
In-Reply-To: <20150313052354.GA9780@boxi.hartikainen.me>

Tuomo Hartikainen wrote:
> On 150312 1835, Dale wrote:
>> wabenbau@gmail.com wrote:
>>> Something similar happened to me. I accidentally pressed F6 while
>>> focused gkrellm but didn't noticed it. Some time later I realized that
>>> the fontsize of gkrellm was increased so that it's height doesn't fit
>>> to the screen anymore. Fist I thought that it has something to do with
>>> the latest update. It took some time till I recognized that I simply
>>> had to press F7 to restore the fontsize to its former height. :-)
>>>
>>> --
>>> Regards
>>> wabe
>>>
>> Well, you should have seen the look on my face the other day when
>> Firefox went FULL SCREEN.  I mean full screen like it does when I hit F
>> and am watching a video.  Heck, I didn't have a menu at the top,  To
>> this day, I have no clue what I did.  I was typing a comment on a social
>> site and all of the sudden, it went sucky.  Still no clue but thank
>> goodness it fixed itself after I killed it and restarted. 
>>
>> Dale
> Try pressing F11 in Firefox? ;)

I think I tried that.  I think I tried all the F* keys.  I was also able
to ctrl F* to get to another desktop and use a second browser to try and
figure the thing out.  I tried a few things I found online but none of
them worked.  Also weird, I was typing normal characters when it went
weird on me just like I am in this email.  No ctrl, alt or other keys. 
The closest I got to those was the shift key for capitol letters. 

I just hope I never run into that again.  o_O 

Dale

:-)  :-) 


  reply	other threads:[~2015-03-13 11:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 18:53 [gentoo-user] heat codes James
2015-02-26 20:13 ` [gentoo-user] " James
2015-02-26 23:02   ` Volker Armin Hemmann
2015-02-27  1:23     ` James
2015-02-27  6:27       ` Volker Armin Hemmann
2015-02-28 11:33   ` Mick
2015-03-12 23:53     ` James
2015-03-13  0:38       ` Dale
2015-03-13  6:20         ` Mick
2015-03-13 11:23           ` Dale
2015-03-13  9:13         ` Peter Humphrey
2015-03-13 11:27           ` Dale
2015-03-13 12:06             ` Peter Humphrey
2015-03-13 15:49               ` Dale
2015-03-13 16:10                 ` Mick
2015-02-26 23:26 ` [gentoo-user] " Dale
2015-02-27  1:31   ` [gentoo-user] " James
2015-02-27  1:48     ` Dale
2015-02-27  5:40       ` Peter Humphrey
2015-02-27  8:27         ` Dale
2015-02-27  9:02           ` Neil Bothwick
2015-02-27  9:43             ` Peter Humphrey
2015-02-27 20:41               ` wabenbau
2015-02-28  9:48                 ` Peter Humphrey
2015-03-12 19:40                   ` Dale
2015-03-12 22:38                     ` Peter Humphrey
2015-03-12 23:12                       ` Neil Bothwick
2015-03-12 23:29                     ` wabenbau
2015-03-12 23:35                       ` Dale
2015-03-13  5:23                         ` Tuomo Hartikainen
2015-03-13 11:31                           ` Dale [this message]
2015-02-27  9:57             ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5502CAA1.6030102@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox