unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Bob Proulx <bob@proulx.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to build the C language environment in Emacs?
Date: Wed, 07 Jan 2015 22:34:59 +0000	[thread overview]
Message-ID: <87r3v6dxt8.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <20150107123019003433623@bob.proulx.com> (message from Bob Proulx on Wed, 7 Jan 2015 12:37:11 -0700)

Bob Proulx <bob@proulx.com> writes:

> Emanuel Berg wrote:
>> Quanyang Liu writes:
>> > Well, in fact, in order to visit some websites, I
>> > need Windows because they are IE only...
>> 
>> Ha ha, stop it. There are no such sites. If there are,
>> I don't want to know their contents...
>
> I have experienced those first hand too.  Usually because the large
> corporate employer I worked for used them for my payroll.  Meaning
> that I could only ignore the IE only site if I didn't want my
> paycheck.  If I wanted my paycheck then it was required to use IE to
> talk to the IE only company payroll website.

I worked for a company that had a complicated and finicky web-based
system for submitting expenses claims.  Some of it only worked in IE and
other bits of it only worked properly in Firefox.  It was necessary to
close the session in one browser and re-open it in another to file a
claim of any complexity.

BR,
Robert Thorpe



  parent reply	other threads:[~2015-01-07 22:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03  4:34 How to build the C language environment in Emacs? Liu Shengyu
2015-01-03  9:04 ` Quanyang Liu
2015-01-03 14:50   ` Grant Rettke
2015-01-06 19:08     ` Ken Goldman
2015-01-03 15:19   ` Filipp Gunbin
2015-01-09 19:21     ` Oleksandr Gavenko
2015-01-03 17:08   ` Óscar Fuentes
2015-01-06 19:05   ` Ken Goldman
     [not found]   ` <mailman.17367.1420571149.1147.help-gnu-emacs@gnu.org>
2015-01-07  1:41     ` Emanuel Berg
2015-01-07  2:21       ` Quanyang Liu
2015-01-07  4:35         ` Óscar Fuentes
     [not found]         ` <mailman.17392.1420605430.1147.help-gnu-emacs@gnu.org>
2015-01-07  4:55           ` Emanuel Berg
2015-01-07 14:16             ` Óscar Fuentes
     [not found]             ` <mailman.17407.1420640515.1147.help-gnu-emacs@gnu.org>
2015-01-07 15:53               ` Will Parsons
2015-01-07 17:48               ` Rusi
2015-01-07 18:08                 ` Óscar Fuentes
2015-01-07 18:12                 ` Eli Zaretskii
     [not found]       ` <mailman.17388.1420597359.1147.help-gnu-emacs@gnu.org>
2015-01-07  3:36         ` Emanuel Berg
2015-01-07 19:37           ` Bob Proulx
2015-01-07 19:58             ` Marcin Borkowski
2015-01-08  2:36               ` Eric Abrahamsen
2015-01-07 22:34             ` Robert Thorpe [this message]
2015-01-07 19:01       ` Ken Goldman
2015-01-03 11:10 ` Eli Zaretskii
     [not found] <mailman.17149.1420274187.1147.help-gnu-emacs@gnu.org>
2015-01-03  8:45 ` Pascal J. Bourguignon
2015-01-03 17:48 ` Emanuel Berg
     [not found] <mailman.17437.1420670116.1147.help-gnu-emacs@gnu.org>
2015-01-07 22:59 ` Pascal J. Bourguignon
2015-01-08 10:23   ` Nicolas Richard

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87r3v6dxt8.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=bob@proulx.com \
    --cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).