unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacsclient not integrated into modern window systems
Date: Sun, 12 Jul 2015 09:21:37 -0700 (PDT)	[thread overview]
Message-ID: <220ab47d-9108-41db-ab08-ceeb31449705@googlegroups.com> (raw)
In-Reply-To: <mailman.6782.1436714885.904.help-gnu-emacs@gnu.org>

On Sunday, July 12, 2015 at 8:58:07 PM UTC+5:30, Vaidheeswaran C wrote:
> On Sunday 12 July 2015 08:07 PM, Eli Zaretskii wrote:
> 
> > There's nothing there except polite explanation of the issue.
> 
> "Not a big deal" is a colloquial expression.  The text books that we
> learn English from doesn't teach us what this expression means.  When
> this is the case, we need to rely on our subjective judgement to
> decide what particular turn of phrase means.  It is also a common
> experience that a phrase that is polite in a conversation is deemed
> otherwise in other cultures.
> 
> When talking across cultures, it is generally considered a good
> practice to err on the conservative side.  It wouldn't have been a big
> deal if the bug was just labelled as Minor.

Hey Vaidheeswaran!
We need not personalize (and cuturalize and nationalize and...) this.
Clearly the *bug* was not welcome in the sense that it is accepted as a bug
but not having sufficient importance to correct it.  That does not spill over
to the *persons* involved

Analogy: Many large projects have code norms. And large enough (and old enough) projects violate these norms left-right-n-center.
And then some OCD guy will come up and want to correct all the indentation or 
misnamings or what-have-you.
So then the others have to tell this super well-meaning but misguided person:
"Thanks but kindly lay off!"

More real example:
Trying to hack inside the python sources I found a bunch of CRLF issues.
[Yeah this is something I am OCD about -- Ive seen 1000s of lines changed because someone used another editor]

Asking around on the mailing lists, people suggested a bug report.
So I filed https://bugs.python.org/issue24507
Then someone suggested making a whole dependency-tree of CRLF bugs.
Now even for an CRLF-OCD this seemed a bit excessive, but I complied...
With https://bugs.python.org/issue24513
which was forthwith closed
[last I knew there is a pdf file checked in as text!]

And in that analogy as here the real issue gets forgotten: things like desktop 
files and the emacsclient paradigm generally are neglected by falling in a
no-mans-land between distro packager and upstream devs


  parent reply	other threads:[~2015-07-12 16:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11  3:24 emacsclient not integrated into modern window systems Rusi
2015-07-11 10:54 ` Rasmus
     [not found] ` <mailman.6717.1436612090.904.help-gnu-emacs@gnu.org>
2015-07-11 11:12   ` Rusi
2015-07-11 16:34     ` Raffaele Ricciardi
2015-07-11 12:20 ` Vaidheeswaran C
     [not found] ` <mailman.6720.1436617209.904.help-gnu-emacs@gnu.org>
2015-07-11 12:24   ` Rusi
2015-07-11 18:59 ` Vaidheeswaran C
2015-07-11 19:08 ` Vaidheeswaran C
2015-07-12  8:54   ` Vaidheeswaran C
     [not found] ` <mailman.6736.1436641200.904.help-gnu-emacs@gnu.org>
2015-07-12  2:57   ` Rusi
2015-07-12  4:28     ` Vaidheeswaran C
     [not found]     ` <mailman.6761.1436675333.904.help-gnu-emacs@gnu.org>
2015-07-12  5:06       ` Rusi
2015-07-12  6:02         ` Vaidheeswaran C
2015-07-12 14:37     ` Eli Zaretskii
2015-07-12 15:08       ` Stefan Monnier
2015-07-12 15:28       ` Vaidheeswaran C
2015-07-12 16:25         ` Eli Zaretskii
     [not found]       ` <mailman.6782.1436714885.904.help-gnu-emacs@gnu.org>
2015-07-12 16:21         ` Rusi [this message]
2015-07-12 16:29           ` Rusi
     [not found]       ` <mailman.6780.1436713709.904.help-gnu-emacs@gnu.org>
2015-07-12 16:32         ` Rusi
2015-07-13  4:59         ` Dan Espen

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=220ab47d-9108-41db-ab08-ceeb31449705@googlegroups.com \
    --to=rustompmody@gmail.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).