unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: riepel@networking.stanford.edu, emacs-pretest-bug@gnu.org,
	eliz@gnu.org, rms@gnu.org
Subject: Re: incomplete comment colorization in terminals
Date: Sat, 15 Mar 2008 01:34:58 -0700	[thread overview]
Message-ID: <200803150834.m2F8YwE6011881@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <18395.21669.736735.483506@kahikatea.snap.net.nz> (Nick Roberts's message of "Sat, 15 Mar 2008 17:46:29 +1300")

Nick Roberts <nickrob@snap.net.nz> writes:

  >  >   >  >   > I tried that in `font-lock-comment-face', and it is ok, 
  >  >   >  > 
  >  >   >  > In that case, please let's go with that solution, it is the lower
  >  >   >  > complexity solution, and less surprising for the user.  We have
  >  >   >  > gotten a few bug reports from users that were confused by this (it is
  >  >   >  > not immediately intuitive).
  >  >   > 
  >  >   > I feel that you're using journalistic techniques to steam roller through
  >  >   > your wishes.  Let's look at the full quote:
  >  >   > 
  >  >   >        I tried that in `font-lock-comment-face', and it is ok, but
  >  >   >        having the text in white is clearer and easier to read.
  >  >   > 
  >  >   > I think it conveys quite a different impression.
  >  >   > 
  >  >   > All these stylistic changes that you are making are probably not worth
  >  >   > arguing about but I think you should look for some real agreement that
  >  >   > they are an improvement before making them.
  >  > 
  >  > Do you have a point here? It's unclear what you are trying to say.
  > 
  > I just think that you are only listening to the parts that you want to
  > hear.  Maybe that's why my message is unclear to you.

OK, I wanted to make sure that you were not trying to make a technical
point, just to attack.

Your behavior is out of line, please keep it off the list and out of my
mailbox too.

Yes, it is customary not quote too much when replying to a message.  In
this case the issue is not that complicated to not remember the whole
context, and don't worry RMS understands perfectly what it is.  And I
hope he gets what I am trying to say too.  We were just having a
technical discussion, as we've have many in the past.
Not sure what exactly you are trying to obtain here, but doing it this
way is not the best.




  reply	other threads:[~2008-03-15  8:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 23:15 incomplete comment colorization in terminals Rob Riepel
2008-03-12  4:26 ` Eli Zaretskii
2008-03-12  6:44   ` Dan Nicolaescu
2008-03-12  8:17     ` Nick Roberts
2008-03-12 13:54       ` Stefan Monnier
2008-03-12 15:07         ` Dan Nicolaescu
2008-03-12 17:51       ` Richard Stallman
2008-03-13  6:38         ` Dan Nicolaescu
2008-03-13 22:24           ` Richard Stallman
2008-03-13 22:44             ` Dan Nicolaescu
2008-03-14  0:21               ` Nick Roberts
2008-03-14  0:34                 ` Dan Nicolaescu
2008-03-15  4:46                   ` Nick Roberts
2008-03-15  8:34                     ` Dan Nicolaescu [this message]
2008-03-15  0:49   ` Rob Riepel
2008-03-15 14:34     ` Eli Zaretskii
2008-03-12  4:45 ` Dan Nicolaescu
2008-03-12 13:57   ` Stefan Monnier
2008-03-13  6:40     ` Dan Nicolaescu
2008-03-13 15:01       ` Stefan Monnier
2008-03-13 18:55         ` Glenn Morris
2008-03-13 21:52           ` Dan Nicolaescu
2008-03-14  4:16           ` Dan Nicolaescu
2008-03-14 15:08             ` Stefan Monnier
2008-03-19  4:02         ` Dan Nicolaescu
2008-03-15  0:50     ` Rob Riepel
2008-03-12 13:10 ` Stefan Monnier

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=200803150834.m2F8YwE6011881@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=riepel@networking.stanford.edu \
    --cc=rms@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).