[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#941058: marked as done (multiline string support)

Your message dated Mon, 30 Sep 2019 19:07:44 -0400
with message-id <87zhilxu0v.fsf@DigitalMercury.dynalias.net>
and subject line Re: Bug#941058: multiline string support
has caused the Debian Bug report #941058,
regarding multiline string support
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.)


-- 
941058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941058
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: elpa-yaml-mode
Version: 0.0.14-1
Severity: wishlist
File: /usr/share/emacs/site-lisp/elpa-src/yaml-mode-0.0.14/yaml-mode.el

In the attached file, yaml-mode indents the multi-line strings incorrectly.
Please fix indentation for multi-line strings.

(At least, ansible complains about the tab stops that yaml-mode suggests.
 I don't know speak yaml fluently, so I may have missed something obvious.)

-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-yaml-mode depends on:
ii  emacsen-common  3.0.4

Versions of packages elpa-yaml-mode recommends:
ii  emacs              1:26.1+1-3.2
ii  emacs-gtk [emacs]  1:26.1+1-3.2

elpa-yaml-mode suggests no packages.

-- no debconf information

# Ref. https://github.com/paluh/ansible-augeas
- hosts: all
  tasks:
    - action: augeas commands='ins ForwardAgent before "/files/etc/ssh/sshd_config"
                               set "/files/etc/ssh/sshd_config/ForwardAgent" "yes"'

    - action: augeas commands='
        ins ForwardAgent before "/files/etc/ssh/sshd_config"
        set "/files/etc/ssh/sshd_config/ForwardAgent" "yes"
        '

--- End Message ---
--- Begin Message --- 
"Trent W. Buck" <trentbuck@gmail.com> writes:

> Nicholas D Steeves wrote:
>> On Tue, 24 Sep 2019 at 01:54, Trent W. Buck <trentbuck@gmail.com> wrote:
>>> In the attached file, yaml-mode indents the multi-line strings incorrectly.
>>> Please fix indentation for multi-line strings.
>>>
>>> (At least, ansible complains about the tab stops that yaml-mode suggests.
>>>  I don't know speak yaml fluently, so I may have missed something obvious.)
>>
>> I'm not familiar with Ansible's syntactic requirements, but the
>> provided example doesn't look right to me.  Here is a link to a few of
>> the different ways to do multiline strings in YAML:
>>   https://stackoverflow.com/questions/3790454/how-do-i-break-a-string-over-multiple-lines
>
> Thanks --  I learned about this after creating the bug report.
>
[snip]
>
> I'm 99% sure I tested all syntaxes and confirmed they all edited lvm.conf correctly.
>

Thank you :-)

> Since the "after" notation works, is easier to read, and is already
> indented correctly by yaml-mode, I no longer care about this ticket.
>

Ok, closing this bug.

>> Also, if it would make your work easier I'm willing to package this:
>>   https://github.com/k1LoW/emacs-ansible
>>
>> Please file a wnpp bug and include me in the X-Debbugs-CC if you'd
>> like me to get to work on that ansible mode.
>
> Thanks, I did not know about this.  I had a quick look.
>

I'll reply to your survey at the RFP bug.  P.S. thank you for taking the
time to evaluate emacs-ansible.


Cheers,
Nicholas

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: