Bug#291951: marked as done (php-elisp: Wrong identation of "or")
Your message dated Tue, 9 Jul 2019 23:55:06 -0400
with message-id <20190710035502.maedy2clubfpcuvo@DigitalMercury.dynalias.net>
and subject line Re: php-elisp: Wrong identation of "or"
has caused the Debian Bug report #291951,
regarding php-elisp: Wrong identation of "or"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
291951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291951
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: php-elisp: Wrong identation of "or"
- From: Cyril Bouthors <cyb@debian.org>
- Date: Mon, 24 Jan 2005 11:33:27 +0300
- Message-id: <873bwrjkfc.fsf@wide.bouthors.org>
Package: php-elisp
Version: 1.1.0-2
Severity: normal
php-elisp makes wrong indentation of the "or" statement, for example
it indents this code like this:
foo()
or die();
foo()
or die();
foo()
or die();
Instead of:
foo()
or die();
foo()
or die();
foo()
or die();
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages php-elisp depends on:
ii emacs21 [emacsen] 21.3+1-8 The GNU Emacs editor
-- no debconf information
<#secure method=pgpmime mode=sign>
--
Cyril Bouthors
--- End Message ---
--- Begin Message ---
- To: 291951-close@bugs.debian.org
- Subject: Re: php-elisp: Wrong identation of "or"
- From: Nicholas D Steeves <nsteeves@gmail.com>
- Date: Tue, 9 Jul 2019 23:55:06 -0400
- Message-id: <20190710035502.maedy2clubfpcuvo@DigitalMercury.dynalias.net>
This bug has been fixed. Closing now.
--- End Message ---
Reply to: