unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: tomas@tuxteam.de
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: General advice beyond Org
Date: Fri, 18 May 2018 09:19:52 -0700	[thread overview]
Message-ID: <CAF-1L2QfwTNpRG5yNJanzGcRe2Dx9APY9x6od0zadatW_JibJA@mail.gmail.com> (raw)
In-Reply-To: <20180518153157.GA18154@tuxteam.de>

I worked as a teacher in a school in a third world context, where the
district was severely underfunded.  I held out as much as I could.  I had
to use proprietary systems, eventually, to report attendance and grades, so
I installed Virtual Box.  It was a long and hard battle: printer drivers
were not up to snuff; networking was difficult compared to the M$
approach.  Back in the day---I started using GNU/Linux in the pre-1.0
kernel days---many things did not work smoothly, but the Linux
Documentation Project was a breath of fresh air, and a beam of light
enlightened the scene.  (As an aside, I note with misgivings that the LDP
is not well maintained---but I am partially responsible for this, because I
didn't work on documentation as perhaps I ought to have.  Then again, the
state of the "Linux Desktop" is such that other supports are available and
many of the hands on configuration and administration tasks are either
automatic or much simpler and more intuitive.).

I would suggest, in your context, that you do not have to abandon free
software, nor, I sense, are you advised to refuse to use the infrastructure
that has been given.  I use emacs for much, I really like org-mode a lot
and even thought I am not able to take advantage of many of the more
sophisticated tools of org-mode.  You may find, like many before you, that
the tools of free and open source software many streamline your workflow,
and give you an edge, even while you are using the ordained tools for your
specific disciplinary work.  When people see that the free and open tools
work for you, gradually you may make inroads, and not at the expense of
your career.

I believe this approach has been behind much of the achieved success of
Free and Open Source software and operating systems.

I am rooting for you.

Alan Davis


On Fri, May 18, 2018 at 8:31 AM, <tomas@tuxteam.de> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, May 18, 2018 at 08:50:32AM -0500, Kevin Buchs wrote:
> > As a student, you simply need to go along with your supervisor's
> > recommendations. You are not in a position to dictate the terms.
>
> Nobody talks about dictating anything. Some supervisors are more
> enlightened than other, so trying to talk to them doesn't seem
> wrong.
>
> >                                                            Using the
> > proprietary tools will not hurt you, unless you need to buy your own.
>
> With that I disagree strongly: free is not primarily about price
> (more so in the OP's case, as he stated clearly). Reducing "free"
> to price totally misses the point, IMO.
>
> [...]
>
> > So, you need to adjust your attitude. It may be that you are presenting
> the
> > issue of principles - I prefer free, you prefer proprietary, but that is
> > not really the true issue. Maybe you don't know the proprietary tools and
> > don't want to learn them or feel you can't learn them. Choice of tools
> you
> > use is no reason to switch graduate programs.
>
> This whole paragraph comes across as somewhat... condescending.
>
> > This is entirely a matter of getting along with other people, not being
> > selfish, etc. These are life skills we are talking about.
>
> Definitely. And part of this getting along is trying to negotiate
> what matters to oneself and to others. I do agree that an intransigent
> attitude isn't helpful, but Edgar didn't show something like that.
>
> Fostering free software is exactly about "not being selfish".
>
> Cheers
> - -- tomás
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAlr+8e0ACgkQBcgs9XrR2kax+wCfbKhTlIUw6n2SL106P2GgS4qa
> SWYAnjKwfLqGw5KnPqBCPPb1GHutiLfQ
> =szdJ
> -----END PGP SIGNATURE-----
>
>


-- 
[Fill in the blanks]

The use of corrupt manipulations and blatant rhetorical ploys ...---
outright lying, flagwaving, personal attacks, setting up phony
alternatives, misdirection, jargon-mongering, evading key issues, feigning
disinterested objectivity, willful misunderstanding of other points of
view---suggests that ... lacks both credibility and evidence.

             ---- Edward Tufte (in context of making presentations)


  reply	other threads:[~2018-05-18 16:19 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  0:28 General advice beyond Org edgar
2018-05-18  1:52 ` Peter Neilson
2018-05-18  2:44   ` [O] " Bob Newell
2018-05-18  7:32     ` tomas
2018-05-18  7:12 ` S. Champailler
2018-05-18  8:10   ` edgar
2018-05-18  8:20     ` tomas
2018-05-18 22:31     ` Stefan Monnier
2018-05-18  8:15   ` tomas
2018-05-18 10:54 ` Yuri Khan
2018-05-18 11:10   ` S. Champailler
2018-05-18 13:50 ` Kevin Buchs
2018-05-18 15:31   ` tomas
2018-05-18 16:19     ` Alan E. Davis [this message]
2018-05-18 16:22       ` Alan E. Davis
2018-05-18 16:32       ` Jason Yamada-Hanff
2018-05-18 19:09         ` Devin Prater
2018-05-18 13:50 ` hymie!
2018-05-19  7:18   ` [O] " Marcin Borkowski
2018-05-20  1:24 ` Samuel Wales
2018-05-20  8:08   ` tomas
     [not found] <mailman.127.1526629283.1290.help-gnu-emacs@gnu.org>
2018-05-18  8:41 ` edgar
2018-05-21 20:10   ` Eric Abrahamsen
2018-05-22  7:10     ` tomas
2018-05-22 16:58       ` Bob Newell
2018-05-22 18:05       ` Eric Abrahamsen
2018-05-22 19:15         ` tomas
     [not found] <mailman.5.1526603344.1292.help-gnu-emacs@gnu.org>
2018-05-18 23:27 ` Gene
2018-05-19  7:06   ` tomas
     [not found]   ` <mailman.67.1526713619.1292.help-gnu-emacs@gnu.org>
2018-05-27  1:02     ` Gene
2018-05-27  7:27       ` tomas
2018-05-19 22:31 ` James K. Lowden
     [not found] <mailman.15.1526832003.3852.help-gnu-emacs@gnu.org>
2018-05-20 19:29 ` edgar
2018-05-21  3:39   ` Marcin Borkowski
     [not found]   ` <mailman.148.1526874026.1292.help-gnu-emacs@gnu.org>
2018-05-21 16:26     ` James K. Lowden
2018-05-21 18:07       ` Bob Newell
2018-05-21 19:23         ` Marcin Borkowski
     [not found] <mailman.19.1527004804.3124.help-gnu-emacs@gnu.org>
2018-05-23  3:44 ` edgar
2018-05-23 19:19   ` Stefan Monnier
2018-05-26  4:14     ` Marcin Borkowski
2018-05-26 19:34       ` Stefan Monnier
2018-05-27  6:54         ` Thien-Thi Nguyen
2018-05-27 17:19           ` Stefan Monnier
2018-05-27 18:19             ` Thien-Thi Nguyen
2018-05-28 19:21               ` Stefan Monnier
2018-05-31  9:50                 ` Thien-Thi Nguyen
     [not found]                 ` <mailman.1113.1528121846.1292.help-gnu-emacs@gnu.org>
2018-06-04 14:46                   ` Emanuel Berg
2018-06-04 14:47                   ` Emanuel Berg
2018-05-27 18:32             ` edgar
2018-05-23  3:50 ` edgar
     [not found] <mailman.626.1526915916.1290.help-gnu-emacs@gnu.org>
2018-05-23  4:04 ` edgar
2018-05-26  4:01   ` Marcin Borkowski
2018-05-26  7:08     ` edgar
     [not found] <mailman.893.1527022341.1290.help-gnu-emacs@gnu.org>
2018-05-23  4:23 ` edgar
2018-05-23  4:27 ` edgar
2018-05-23  4:30 ` edgar

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=CAF-1L2QfwTNpRG5yNJanzGcRe2Dx9APY9x6od0zadatW_JibJA@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tomas@tuxteam.de \
    /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).