unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: emacs-pretest-bug@gnu.org, 1212@emacsbugs.donarmstrong.com
Subject: bug#1212: 23.0.60; split-string-and-unquote problems
Date: Tue, 21 Oct 2008 15:36:52 +0200	[thread overview]
Message-ID: <u3aiqgjd7.fsf@gnu.org> (raw)
In-Reply-To: <je8wsihyis.fsf@sykes.suse.de>

> From: Andreas Schwab <schwab@suse.de>
> Cc: 1212@emacsbugs.donarmstrong.com, emacs-pretest-bug@gnu.org
> Date: Tue, 21 Oct 2008 15:24:11 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,
> >> 	DNS_FROM_SECURITYSAGE autolearn=no version=3.1.0
> >> From: Andreas Schwab <schwab@suse.de>
> >> Cc: 1212@emacsbugs.donarmstrong.com, emacs-pretest-bug@gnu.org
> >> Date: Tue, 21 Oct 2008 14:50:30 +0200
> >> 
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> > The answer to that specific question is completely irrelevant to the
> >> > problem I reported in the original bug report.  You need to consider
> >> > all the examples and questions together.
> >> 
> >> It makes half of your examples useless.
> >
> > I made a lot of trials out of sheer despair.  The examples were
> > supposed to demonstrate that nothing worked.
> 
> Of course, if there is nothing to split.  What's your point?

The point is that the function says it also _unquotes_.  It's the
unquoting that didn't work for me in the cases I described in the bug
report.  Adding more text just so it could split doesn't change the
problematic behavior, but would clutter the bug report with irrelevant
details.






  reply	other threads:[~2008-10-21 13:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 16:04 bug#1212: 23.0.60; split-string-and-unquote problems Eli Zaretskii
2008-10-20 17:01 ` Andreas Schwab
2008-10-20 19:06   ` Eli Zaretskii
2008-10-20 21:30     ` Andreas Schwab
2008-10-20 22:36       ` Eli Zaretskii
2008-10-21  9:25         ` Andreas Schwab
2008-10-21 10:18           ` Eli Zaretskii
2008-10-21 11:00             ` Andreas Schwab
2008-10-21 11:33               ` Eli Zaretskii
2008-10-21 11:49                 ` Andreas Schwab
2008-10-21 12:25                   ` Eli Zaretskii
2008-10-21 12:50                     ` Andreas Schwab
2008-10-21 12:58                       ` Eli Zaretskii
2008-10-21 13:24                         ` Andreas Schwab
2008-10-21 13:36                           ` Eli Zaretskii [this message]
2008-10-21 13:44                             ` Andreas Schwab
2008-10-21 15:13                               ` Eli Zaretskii
2008-10-20 17:08 ` Andreas Schwab
2008-10-20 19:16   ` Eli Zaretskii
2008-10-20 21:28     ` Andreas Schwab
2008-10-20 22:53       ` Eli Zaretskii
2008-10-20 22:53       ` Eli Zaretskii
     [not found]       ` <u63nmj2tx.fsf@gnu.org>
2008-10-21  1:11         ` Stefan Monnier
2008-10-21  1:11         ` 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=u3aiqgjd7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=1212@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=schwab@suse.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.
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).