unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean-Christophe Helary <brandelune@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: concat vs format
Date: Mon, 10 Dec 2018 00:44:55 +0900	[thread overview]
Message-ID: <37918DFE-4549-49E7-ABA2-99CF8D3C0D0E@gmail.com> (raw)
In-Reply-To: <87lg4yoii8.fsf@gmx.net>



> On Dec 9, 2018, at 23:57, Stephen Berman <stephen.berman@gmx.net> wrote:
> 
>> Result: "/Users/suzume/Documents/Code/brandelune.github.io/ <http://brandelune.github.io/>..."
>> 
>> So, the last concat gives me a path that's not the result of a
>> "concat" on the values that I feed it. Why ?
> 
> The length of the output in Edebug is constrained by the user option
> edebug-print-length, which is 50 by default; by setting that variable to
> nil, the output won't be cut off.

Thank you Stephan.

I found out that my issue had nothing to do with concat/format but rather with let*/setq.

My first code ran fine with setq, then, after the thread that I started about setq a few days ago, I decided to use let* and let in my code instead. And that's when things started to break. I don't understand why (must be something with variable scope) but for now I need to write something that works and move on.

I'll come back here when I am closer to identifying my issue.


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune




      reply	other threads:[~2018-12-09 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-09  3:50 concat vs format Jean-Christophe Helary
2018-12-09  4:09 ` Drew Adams
2018-12-09 10:02   ` Jean-Christophe Helary
2018-12-09 11:30     ` Stefan Huchler
2018-12-09 13:42       ` Jean-Christophe Helary
2018-12-09 14:15         ` Stefan Monnier
2018-12-09 14:55           ` Jean-Christophe Helary
2018-12-09 14:57         ` Stephen Berman
2018-12-09 15:44           ` Jean-Christophe Helary [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

  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=37918DFE-4549-49E7-ABA2-99CF8D3C0D0E@gmail.com \
    --to=brandelune@gmail.com \
    --cc=help-gnu-emacs@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.
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).