Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Eli Zaretskii <eliz@elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Word break characters are language dependent
Date: Mon, 22 Sep 2003 07:24:00 -0000	[thread overview]
Message-ID: <3F6EA3BF.7040908@redhat.com> (raw)
In-Reply-To: <20030921214323.GE15984@gnat.com>

> Other than that, I think your general idea is correct and the proposed
>> direction is reasonable.
> 
> 
> Thanks for your input, it is much appreciated. I'll wait for another
> week to see if I can get more feedback, and then will try to work on
> a patch.

You mean: This whole idea of language sensative tab-expansion, while 
sensible, makes my brain hurt :-)




      parent reply	other threads:[~2003-09-22  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 19:16 Joel Brobecker
2003-09-21 12:32 ` Eli Zaretskii
2003-09-21 21:43   ` Joel Brobecker
2003-09-22  5:14     ` Eli Zaretskii
2003-09-23 18:35       ` Joel Brobecker
2003-09-24  5:34         ` Eli Zaretskii
2003-09-24 18:13           ` Joel Brobecker
2003-09-22  7:24     ` Andrew Cagney [this message]

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

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

  git send-email \
    --in-reply-to=3F6EA3BF.7040908@redhat.com \
    --to=ac131313@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    /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