From: pietru@caramail.com
To: tomas@tuxteam.de
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Optional Arguments
Date: Mon, 7 Dec 2020 19:13:06 +0100 [thread overview]
Message-ID: <trinity-d06c5b96-ffac-460d-8ea6-1c56e7d6d488-1607364786154@3c-app-mailcom-bs11> (raw)
In-Reply-To: <20201207153847.GB15617@tuxteam.de>
I'm having a go at returning the two values from a function
(defun word-markers ()
(let ((ma mb))
(skip-chars-backward "[:alpha:]")
(setq ma (point))
(skip-chars-forward "[:alpha:]")
(setq mb (point))
(cons ma mb) ))
(defun test ()
(interactive)
(let ((deactivate-mark nil) bounds $ma $mb)
(if (use-region-p)
(setq $ma (region-beginning) $mb (region-end))
(save-excursion
(setq bounds (word-markers))
(setq $mu (car bounds))
(setq $mv (car bounds)) ))
(message "Bounds: %s" $bounds)
(message "Region: [%s, %s]" $ma $mb) ))
But something's not right.
> Sent: Monday, December 07, 2020 at 4:38 PM
> From: tomas@tuxteam.de
> To: pietru@caramail.com
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Optional Arguments
>
> On Mon, Dec 07, 2020 at 03:24:36PM +0100, pietru@caramail.com wrote:
>
> [...]
>
> > > => "ma: 15 mb: 26"
> >
> > Hmmm. Variables local to function.
>
> Yes. "Local" meaning here either dynamical extent (called functions
> "see" the variables up the call chain, think Unix shells) or
> lexical extent (code contexts "see" the variables of enclosing
> code contexts (think C or Java or...), depending on whether you
> chose lexical binding [1].
>
> [...]
>
> > > ...would you expect it to change the number 15 to whatever the word's
> > > beginning position is? You would mess up maths with that :)
> >
> > Yes, it would mess up.
>
> Gödel's nothing against that :-D
>
> Cheers
>
> [1] Cf. Chapter "Lexical Binding" in the Elisp manual, or here
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Lexical-Binding.html
>
> - t
>
next prev parent reply other threads:[~2020-12-07 18:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 3:17 Optional Arguments pietru
2020-12-07 8:16 ` Alexis Roda
2020-12-07 12:37 ` pietru
2020-12-07 13:06 ` tomas
2020-12-07 13:35 ` Anders Dalskov
2020-12-07 14:24 ` pietru
2020-12-07 15:38 ` tomas
2020-12-07 18:13 ` pietru [this message]
2020-12-07 19:01 ` Arthur Miller
2020-12-07 19:42 ` pietru
2020-12-07 19:54 ` Michael Heerdegen
2020-12-07 20:21 ` pietru
2020-12-07 20:52 ` Arthur Miller
2020-12-07 21:21 ` pietru
2020-12-07 19:51 ` Alexis Roda
2020-12-07 15:06 ` pietru
2020-12-07 15:51 ` tomas
2020-12-07 17:51 ` pietru
2020-12-07 18:33 ` Arthur Miller
2020-12-07 18:49 ` pietru
2020-12-07 20:13 ` Stefan Monnier
2020-12-07 20:25 ` pietru
2020-12-07 20:39 ` Christopher Dimech
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=trinity-d06c5b96-ffac-460d-8ea6-1c56e7d6d488-1607364786154@3c-app-mailcom-bs11 \
--to=pietru@caramail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.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.
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).