unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: How to build the C language environment in Emacs?
Date: Thu, 08 Jan 2015 10:36:53 +0800	[thread overview]
Message-ID: <878uheq9q2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87d26qz7ks.fsf@wmi.amu.edu.pl

Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:

> On 2015-01-07, at 20:37, Bob Proulx <bob@proulx.com> wrote:
>
>> 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.
>
> Unfortunately, I have to confirm the sightings of these...  Not exactly
> my payroll, but some e-learning materials (not done by me) which had
> good content, but ran only on IE.
>
>> Bob

Online banking websites in large swathes of Asia. Try getting around
that!

Actually I take that back, the advent of Android apps has obviated the
problem to a large extent.




  reply	other threads:[~2015-01-08  2:36 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 [this message]
2015-01-07 22:34             ` Robert Thorpe
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=878uheq9q2.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).