all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 34749@debbugs.gnu.org
Subject: bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) candidates
Date: Sat, 9 Mar 2019 14:32:48 -0800 (PST)	[thread overview]
Message-ID: <8ad1ebef-d63d-492f-a542-05c66bca6ad2@default> (raw)
In-Reply-To: <<83sgvv7w99.fsf@gnu.org>>

> > > > I wonder if it would help to give an example where
> > > > we show correspondence between a spec that uses a
> > > > string argument to `interactive' that specifies a
> > > > few args to the function, of different types, and
> > > > a spec that uses a Lisp sexp, which when evaluated
> > > > produces a list of those same args.
> > >
> > > There's an example right after that text.
> >
> > I don't see an example that shows the correspondence
> > between a string arg and a Lisp sexp arg that returns
> > a list of args.
> 
> Why is it important what types are the arguments?  The issue was the
> significance of the newline in the interactive spec string, and that
> is independent of the types of the arguments.

I don't think anyone said that it's important what
types the arguments are or whether arguments of
different types are used in the examples.

I suggested that we show correspondence between use
of a string spec and a Lisp sexp, and do so with the
use of more than one arg (so "\n" in the string spec).

Martin has not answered wrt whether he thinks doing
this would have helped him understand better.

Apparently he did not initially understand this well.
You asked him to say what parts he didn't understand
well.  I made a suggestion, guessing that it might
help.

I don't choose to argue with you about this.  Just
trying to help.





  parent reply	other threads:[~2019-03-09 22:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
     [not found] ` <<<83o96lacf8.fsf@gnu.org>
     [not found]   ` <<6aae54ec-85bf-4447-bec0-7c916caeb2f8@default>
     [not found]     ` <<83a7i59u85.fsf@gnu.org>
2019-03-08 17:14       ` bug#34749: 26.1; `delete-windows-on': (1) doc, (2) bug, (3) bug, (4) candidates Drew Adams
2019-03-08 18:58         ` Eli Zaretskii
     [not found] ` <<<5C7E4BAB.3050508@gmx.at>
     [not found]   ` <<<83mum5accd.fsf@gnu.org>
     [not found]     ` <<<5C824BAC.4090907@gmx.at>
     [not found]       ` <<<83lg1pa4oa.fsf@gnu.org>
     [not found]         ` <<<5C82B9E1.1080302@gmx.at>
     [not found]           ` <<<83zhq587g6.fsf@gnu.org>
     [not found]             ` <<<5C837BD6.9010200@gmx.at>
     [not found]               ` <<<83ef7g8gbc.fsf@gnu.org>
     [not found]                 ` <<<5C83BC9B.5020803@gmx.at>
     [not found]                   ` <<<e0b90f9b-2d1f-4877-b83a-aeca5425dbea@default>
     [not found]                     ` <<<8336nw807g.fsf@gnu.org>
     [not found]                       ` <<dd8e2b24-ab4a-4a4c-b9b8-9249f9ec035b@default>
     [not found]                         ` <<83sgvv7w99.fsf@gnu.org>
2019-03-09 22:32                           ` Drew Adams [this message]
     [not found] <<<<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
     [not found] ` <<<<83o96lacf8.fsf@gnu.org>
     [not found]   ` <<<6aae54ec-85bf-4447-bec0-7c916caeb2f8@default>
     [not found]     ` <<<83a7i59u85.fsf@gnu.org>
     [not found]       ` <<a1314708-0feb-4092-8b60-37d7282a328f@default>
     [not found]         ` <<834l8d9orm.fsf@gnu.org>
2019-03-08 19:48           ` Drew Adams
2019-03-08 20:14             ` Eli Zaretskii
     [not found] <<b375da42-2b65-4579-902c-85e9fdcaeac7@default>
     [not found] ` <<83o96lacf8.fsf@gnu.org>
2019-03-08 16:34   ` Drew Adams
2019-03-08 17:00     ` Eli Zaretskii
     [not found] ` <<5C7E4BAB.3050508@gmx.at>
     [not found]   ` <<83mum5accd.fsf@gnu.org>
     [not found]     ` <<5C824BAC.4090907@gmx.at>
     [not found]       ` <<83lg1pa4oa.fsf@gnu.org>
     [not found]         ` <<5C82B9E1.1080302@gmx.at>
     [not found]           ` <<83zhq587g6.fsf@gnu.org>
     [not found]             ` <<5C837BD6.9010200@gmx.at>
     [not found]               ` <<83ef7g8gbc.fsf@gnu.org>
     [not found]                 ` <<5C83BC9B.5020803@gmx.at>
     [not found]                   ` <<e0b90f9b-2d1f-4877-b83a-aeca5425dbea@default>
     [not found]                     ` <<8336nw807g.fsf@gnu.org>
2019-03-09 17:35                       ` Drew Adams
2019-03-09 18:12                         ` Eli Zaretskii
2019-03-04 16:25 Drew Adams
2019-03-05 10:12 ` martin rudalics
2019-03-08 10:29   ` Eli Zaretskii
2019-03-08 11:02     ` martin rudalics
2019-03-08 13:15       ` Eli Zaretskii
2019-03-08 18:52         ` martin rudalics
2019-03-08 19:45           ` Drew Adams
2019-03-09  8:39             ` martin rudalics
2019-03-09 16:37               ` Drew Adams
2019-03-08 19:58           ` Eli Zaretskii
2019-03-09  8:39             ` martin rudalics
2019-03-09 10:58               ` Eli Zaretskii
2019-03-09 13:16                 ` martin rudalics
2019-03-09 16:33                   ` Drew Adams
2019-03-09 16:46                     ` Eli Zaretskii
2019-03-10  8:46                     ` martin rudalics
2019-03-10  8:48                 ` martin rudalics
2019-03-08 10:27 ` Eli Zaretskii
2022-04-26 12:32 ` Lars Ingebrigtsen

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=8ad1ebef-d63d-492f-a542-05c66bca6ad2@default \
    --to=drew.adams@oracle.com \
    --cc=34749@debbugs.gnu.org \
    --cc=eliz@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.