all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James Nguyen <jamesn@fastmail.com>
To: Ingo Lohmar <i.lohmar@gmail.com>
Cc: 27503@debbugs.gnu.org
Subject: bug#27503: 26.0.50; Not lining up Javascript arguments
Date: Tue, 27 Jun 2017 17:45:30 -0700	[thread overview]
Message-ID: <BBAC6155-EE7E-4DB9-81D2-C35FDE51509C@fastmail.com> (raw)
In-Reply-To: <87d19p6tz1.fsf@acer.localhost.com>

No problem, I was just confirming.

I prefer your snippet anyhow.

> On Jun 27, 2017, at 1:44 PM, Ingo Lohmar <i.lohmar@gmail.com> wrote:
> 
> On Tue, Jun 27 2017 12:42 (-0700), James Nguyen wrote:
> 
>> This would effectively be the same as my snippet right? I removed the if
>> check and the else block to always go into the progn.
> 
> You're right, and I am sorry for my bad choice of words, I did not mean
> to imply otherwise.  In fact I have to admit I did not check your code
> in detail, I just noticed that the behavior was fixed (like you stated).
> 
> Thanks for starting the bug report, I would be happy if that change
> would land in Emacs.






  reply	other threads:[~2017-06-28  0:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27  1:49 bug#27503: 26.0.50; Not lining up Javascript arguments James Nguyen
2017-06-27 18:16 ` Ingo Lohmar
2017-06-27 19:42   ` James Nguyen
2017-06-27 20:44     ` Ingo Lohmar
2017-06-28  0:45       ` James Nguyen [this message]
2017-06-28 10:36     ` Dmitry Gutov
2017-06-28 10:57     ` Nicolas Petton
2017-06-28 10:35   ` Dmitry Gutov
2017-06-28 14:56     ` Ingo Lohmar
2017-06-29  0:52       ` Dmitry Gutov
2017-07-01 11:23         ` Ingo Lohmar
2017-07-03  2:11           ` Dmitry Gutov
2017-07-03 18:05             ` Ingo Lohmar
2017-07-03 18:21               ` Ingo Lohmar
2017-07-03 21:01                 ` Dmitry Gutov
2017-07-03 23:14                   ` James Nguyen
2017-07-03 20:17               ` Dmitry Gutov

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=BBAC6155-EE7E-4DB9-81D2-C35FDE51509C@fastmail.com \
    --to=jamesn@fastmail.com \
    --cc=27503@debbugs.gnu.org \
    --cc=i.lohmar@gmail.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.
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.