unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
* Indentation with inline comments in Emacs
@ 2022-04-16 12:12 Zelphir Kaltstahl
  2022-04-16 14:57 ` Jérémy Korwin-Zmijowski
  2022-04-17  3:03 ` Taylan Kammer
  0 siblings, 2 replies; 12+ messages in thread
From: Zelphir Kaltstahl @ 2022-04-16 12:12 UTC (permalink / raw)
  To: guile-user

Hello Guile users!

The subject might not be only Guile related, but I figure, that many on this 
mailing list are using Emacs for writing Guile code. I wonder, if anyone has 
some trick for fixing the following indentation issue:

Sometimes I want to put inline comments with #||# in things like lists, 
arguments for function calls or vectors. For example I want to write the name of 
the month next to the number of days of that month, in a vector creation. Here 
is the example:

~~~~
(define DAYS-IN-MONTH
   #(#|January|# 31
                 #|February|# 28
                              #|March|# 31 #|April|# 30 #|May|# 31 #|June|# 30 #|July|# 31 #|August|# 30
                               30 30))
~~~~

As you can see, the indentation is adjusted each line according to the 
non-comment thing on the previous line, when I press TAB or whatever other key 
binding one has for indentation. However, in this case I would rather want it to 
adjust indentation. Is there a quick fix for this? Or some way to make Emacs 
understand this as a separate case and have it indent "correctly"? Does anyone 
have a solution?

Regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-16 12:12 Indentation with inline comments in Emacs Zelphir Kaltstahl
@ 2022-04-16 14:57 ` Jérémy Korwin-Zmijowski
  2022-04-17 10:49   ` Zelphir Kaltstahl
  2022-04-17  3:03 ` Taylan Kammer
  1 sibling, 1 reply; 12+ messages in thread
From: Jérémy Korwin-Zmijowski @ 2022-04-16 14:57 UTC (permalink / raw)
  To: guile-user

Yo Zelphir,

I would replace numbers with a constant name which avoid the need for comments.

Sorry, not an Emacs solution. I just keep comments for outside context.

Cheers!


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-16 12:12 Indentation with inline comments in Emacs Zelphir Kaltstahl
  2022-04-16 14:57 ` Jérémy Korwin-Zmijowski
@ 2022-04-17  3:03 ` Taylan Kammer
  2022-04-17 11:06   ` Zelphir Kaltstahl
  1 sibling, 1 reply; 12+ messages in thread
From: Taylan Kammer @ 2022-04-17  3:03 UTC (permalink / raw)
  To: Zelphir Kaltstahl, guile-user

On 16.04.2022 14:12, Zelphir Kaltstahl wrote:
> Hello Guile users!
> 
> The subject might not be only Guile related, but I figure, that many on this mailing list are using Emacs for writing Guile code. I wonder, if anyone has some trick for fixing the following indentation issue:
> 
> Sometimes I want to put inline comments with #||# in things like lists, arguments for function calls or vectors. For example I want to write the name of the month next to the number of days of that month, in a vector creation. Here is the example:
> 
> ~~~~
> (define DAYS-IN-MONTH
>   #(#|January|# 31
>                 #|February|# 28
>                              #|March|# 31 #|April|# 30 #|May|# 31 #|June|# 30 #|July|# 31 #|August|# 30
>                               30 30))
> ~~~~
> 
> As you can see, the indentation is adjusted each line according to the non-comment thing on the previous line, when I press TAB or whatever other key binding one has for indentation. However, in this case I would rather want it to adjust indentation. Is there a quick fix for this? Or some way to make Emacs understand this as a separate case and have it indent "correctly"? Does anyone have a solution?
> 
> Regards,
> Zelphir
> 

To be honest, the easiest thing to do here is probably use a different comment style.

In this particular example I would probably just go full vertical:

  (define DAYS-IN-MONTH
    #(31 ;january
      28 ;february
      31 ;march
      30 ;april
      31 ;may
      ;; ...
    )

I know it doesn't fulfill your requirement, but usually I find it wise to use the
"path of least resistance" when it comes to how an editor/IDE wants to format code
and just go with the rules it has.  Makes life easier for others who might not have
whatever custom configuration you add to your editor to bend it to your will.


Tangential:

I've also tried out a "columns" variant with multiple numbers per row and a comment
above each row identifying the numbers, but Emacs seems to insist on special-casing
the first column in that case, regardless of comments, like this:

  (define days
    #(31      28       31
              30       31          30
              xx       yy          zz
              ;; ...
              ))

That's already ugly without comments, and IMO a significant issue.

Maybe it would be good to teach Emacs to indent lists/vectors that don't represent
a function/macro call.  This indentation clearly assumes that the leading "31" in
the vector is the operator, and the rest of the vector operands.

It should probably not assume that for vectors #(...) and quoted lists '(...).

-- 
Taylan



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-16 14:57 ` Jérémy Korwin-Zmijowski
@ 2022-04-17 10:49   ` Zelphir Kaltstahl
  2022-04-17 13:44     ` Luis Felipe
  0 siblings, 1 reply; 12+ messages in thread
From: Zelphir Kaltstahl @ 2022-04-17 10:49 UTC (permalink / raw)
  To: guile-user

Hello Jérémy!

On 4/16/22 16:57, Jérémy Korwin-Zmijowski wrote:
> Yo Zelphir,
>
> I would replace numbers with a constant name which avoid the need for comments.
>
> Sorry, not an Emacs solution. I just keep comments for outside context.
>
> Cheers!

This is an idea. I'll consider that approach!

I have the same indentation issue though, when I use #||# comments for 
arguments, which are not keyword arguments, but I want to hint what they are 
used for. One could argue, that I should rewrite the called function to use 
keyword arguments, or, if it is a library function, I should wrap it. Hmmm. 
Maybe that's a valid point.

Thanks for the input!
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-17  3:03 ` Taylan Kammer
@ 2022-04-17 11:06   ` Zelphir Kaltstahl
  2022-04-17 14:58     ` Maxime Devos
  0 siblings, 1 reply; 12+ messages in thread
From: Zelphir Kaltstahl @ 2022-04-17 11:06 UTC (permalink / raw)
  To: Taylan Kammer; +Cc: guile-user

Hello Taylan!

On 4/17/22 05:03, Taylan Kammer wrote:
> On 16.04.2022 14:12, Zelphir Kaltstahl wrote:
>> Hello Guile users!
>>
>> The subject might not be only Guile related, but I figure, that many on this mailing list are using Emacs for writing Guile code. I wonder, if anyone has some trick for fixing the following indentation issue:
>>
>> Sometimes I want to put inline comments with #||# in things like lists, arguments for function calls or vectors. For example I want to write the name of the month next to the number of days of that month, in a vector creation. Here is the example:
>>
>> ~~~~
>> (define DAYS-IN-MONTH
>>    #(#|January|# 31
>>                  #|February|# 28
>>                               #|March|# 31 #|April|# 30 #|May|# 31 #|June|# 30 #|July|# 31 #|August|# 30
>>                                30 30))
>> ~~~~
>>
>> As you can see, the indentation is adjusted each line according to the non-comment thing on the previous line, when I press TAB or whatever other key binding one has for indentation. However, in this case I would rather want it to adjust indentation. Is there a quick fix for this? Or some way to make Emacs understand this as a separate case and have it indent "correctly"? Does anyone have a solution?
>>
>> Regards,
>> Zelphir
>>
> To be honest, the easiest thing to do here is probably use a different comment style.
>
> In this particular example I would probably just go full vertical:
>
>    (define DAYS-IN-MONTH
>      #(31 ;january
>        28 ;february
>        31 ;march
>        30 ;april
>        31 ;may
>        ;; ...
>      )
>
> I know it doesn't fulfill your requirement, but usually I find it wise to use the
> "path of least resistance" when it comes to how an editor/IDE wants to format code
> and just go with the rules it has.  Makes life easier for others who might not have
> whatever custom configuration you add to your editor to bend it to your will.
Good point! For some reason I always shun the single semi-colon comments. I 
think that is, because I usually start writing such a comment and then notice, 
that the comment will make the line very long, so I want to break it. However, 
to break it, it makes more sense to have the comment above the line and use 
double semi-colon. In this case however, the single semi-colon does actually 
seem like a good alternative.
> Tangential:
>
> I've also tried out a "columns" variant with multiple numbers per row and a comment
> above each row identifying the numbers, but Emacs seems to insist on special-casing
> the first column in that case, regardless of comments, like this:
>
>    (define days
>      #(31      28       31
>                30       31          30
>                xx       yy          zz
>                ;; ...
>                ))
>
> That's already ugly without comments, and IMO a significant issue.
>
> Maybe it would be good to teach Emacs to indent lists/vectors that don't represent
> a function/macro call.  This indentation clearly assumes that the leading "31" in
> the vector is the operator, and the rest of the vector operands.
>
> It should probably not assume that for vectors #(...) and quoted lists '(...).

I never understood, why Emacs indented that way, but now I understand. First 
argument is seen as special, as the function/procedure that is being called – 
aha! I do not know, whether the syntax for vector creation #(...) is the same in 
all Scheme dialects, which have vectors, in general. Perhaps it would require a 
specific GNU Guile mode for Emacs, if it is not the same in all Scheme dialects.

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-17 10:49   ` Zelphir Kaltstahl
@ 2022-04-17 13:44     ` Luis Felipe
  2022-04-18 10:48       ` Zelphir Kaltstahl
  0 siblings, 1 reply; 12+ messages in thread
From: Luis Felipe @ 2022-04-17 13:44 UTC (permalink / raw)
  To: Zelphir Kaltstahl; +Cc: guile-user


[-- Attachment #1.1: Type: text/plain, Size: 1487 bytes --]

Hi Zelphir,

On Sunday, April 17th, 2022 at 10:49 AM, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:

> I have the same indentation issue though, when I use #||# comments for
> arguments, which are not keyword arguments, but I want to hint what they are
> used for. One could argue, that I should rewrite the called function to use
> keyword arguments, or, if it is a library function, I should wrap it. Hmmm.
> Maybe that's a valid point.

Or document the function and its parameter using a documentation string (docstring) instead of comments? This way, you or the users of your code can read that documentation with Emacs Geiser.

For instance:

(define (get-field record field)
  "Get the value of FIELD from RECORD.

  RECORD (Guile Record or SRFI 9 Record)
    A record of any type.

  FIELD (Symbol)
    The name of the field.

  RETURN VALUE (Anything)
    The value of the field.

  If the FIELD does not exist, a no-such-field exception is raised."
  (let* [(descriptor (record-type-descriptor record))
         (access-field (record-accessor descriptor field))]

    (access-field record)))

Then, in Emacs, when calling this procedure, you would place the caret in get-field, press C-c C-d C-d, and Emacs would show its documentation in a buffer.

That's my documentation style, though, which is not conventional, but just an example.

Using documentation string is also useful if you later want to [auto]generate API documentation.

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-17 11:06   ` Zelphir Kaltstahl
@ 2022-04-17 14:58     ` Maxime Devos
  2022-04-18 10:49       ` Zelphir Kaltstahl
  0 siblings, 1 reply; 12+ messages in thread
From: Maxime Devos @ 2022-04-17 14:58 UTC (permalink / raw)
  To: Zelphir Kaltstahl, Taylan Kammer; +Cc: guile-user

[-- Attachment #1: Type: text/plain, Size: 622 bytes --]

Zelphir Kaltstahl schreef op zo 17-04-2022 om 11:06 [+0000]:
> I never understood, why Emacs indented that way, but now I understand. First 
> argument is seen as special, as the function/procedure that is being called – 
> aha! I do not know, whether the syntax for vector creation #(...) is the same in 
> all Scheme dialects, which have vectors, in general. Perhaps it would require a 
> specific GNU Guile mode for Emacs, if it is not the same in all Scheme dialects.

#(vector things ...) is standard R6RS scheme:

http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-7.html#node_sec_4.3.3

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-17 13:44     ` Luis Felipe
@ 2022-04-18 10:48       ` Zelphir Kaltstahl
  2022-04-18 13:33         ` Ricardo G. Herdt
  2022-04-18 14:05         ` Luis Felipe
  0 siblings, 2 replies; 12+ messages in thread
From: Zelphir Kaltstahl @ 2022-04-18 10:48 UTC (permalink / raw)
  To: Luis Felipe; +Cc: guile-user

Hello Felipe!

On 4/17/22 15:44, Luis Felipe wrote:
> Hi Zelphir,
>
> On Sunday, April 17th, 2022 at 10:49 AM, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
>
>> I have the same indentation issue though, when I use #||# comments for
>> arguments, which are not keyword arguments, but I want to hint what they are
>> used for. One could argue, that I should rewrite the called function to use
>> keyword arguments, or, if it is a library function, I should wrap it. Hmmm.
>> Maybe that's a valid point.
> Or document the function and its parameter using a documentation string (docstring) instead of comments? This way, you or the users of your code can read that documentation with Emacs Geiser.
>
> For instance:
>
> (define (get-field record field)
>    "Get the value of FIELD from RECORD.
>
>    RECORD (Guile Record or SRFI 9 Record)
>      A record of any type.
>
>    FIELD (Symbol)
>      The name of the field.
>
>    RETURN VALUE (Anything)
>      The value of the field.
>
>    If the FIELD does not exist, a no-such-field exception is raised."
>    (let* [(descriptor (record-type-descriptor record))
>           (access-field (record-accessor descriptor field))]
>
>      (access-field record)))
>
> Then, in Emacs, when calling this procedure, you would place the caret in get-field, press C-c C-d C-d, and Emacs would show its documentation in a buffer.
>
> That's my documentation style, though, which is not conventional, but just an example.
>
> Using documentation string is also useful if you later want to [auto]generate API documentation.

It is a good idea to document ones code, of course, even for future self : )

Usually when I `M-x run-geiser RET` or `M-x run-geiser RET` and then move the 
cursor into a function call and the function is somehow available to Geiser, I 
see a line at the bottom of my Emacs, which lists the arguments and highlights 
the argument, which I should be filling in next. That is already very helpful.

However, this is all assuming, that everyone uses Emacs. Comments would be more 
universally accessible. (I know it sounds almost crazy not to use Emacs for 
coding Guile ;D) That would help others, who do not use Emacs as well.

I like the documentation style in the doc string you are proposing. Not sure I 
will always go to that length myself, but it would probably be a good practice. 
Just like you said, for generating auto-generating things like API docs. Btw.: 
What is the standard tool in the Guile ecosystem to do that from doc strings 
like yours?

Also thanks for the C-c C-d C-d hint. I did not know the shortcut.

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-17 14:58     ` Maxime Devos
@ 2022-04-18 10:49       ` Zelphir Kaltstahl
  0 siblings, 0 replies; 12+ messages in thread
From: Zelphir Kaltstahl @ 2022-04-18 10:49 UTC (permalink / raw)
  To: Maxime Devos; +Cc: guile-user

Hi Maxime!

On 4/17/22 16:58, Maxime Devos wrote:
> Zelphir Kaltstahl schreef op zo 17-04-2022 om 11:06 [+0000]:
>> I never understood, why Emacs indented that way, but now I understand. First
>> argument is seen as special, as the function/procedure that is being called –
>> aha! I do not know, whether the syntax for vector creation #(...) is the same in
>> all Scheme dialects, which have vectors, in general. Perhaps it would require a
>> specific GNU Guile mode for Emacs, if it is not the same in all Scheme dialects.
> #(vector things ...) is standard R6RS scheme:
>
> http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-7.html#node_sec_4.3.3
>
> Greetings,
> Maxime.

I see! Thanks for that info : ) So that means it might even make sense in Emacs' 
general Scheme mode.

Regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-18 10:48       ` Zelphir Kaltstahl
@ 2022-04-18 13:33         ` Ricardo G. Herdt
  2022-04-18 14:09           ` Luis Felipe
  2022-04-18 14:05         ` Luis Felipe
  1 sibling, 1 reply; 12+ messages in thread
From: Ricardo G. Herdt @ 2022-04-18 13:33 UTC (permalink / raw)
  To: guile-user

Hi Zelphir,

actually the doc-strings are available during runtime using '(ice-9 
documentation)', so theoretically it is not restricted to Emacs. In fact 
I have been working on my spare time on a LSP server for scheme 
(together with a emacs-lsp and a VS Code extension), and documentation 
of guile functions was quite straight-forward to implement. It's not yet 
ready for prime time though.

Regards,

Ricardo

Am 18.04.2022 12:48 schrieb Zelphir Kaltstahl:
> Hello Felipe!
> 
> On 4/17/22 15:44, Luis Felipe wrote:
>> Hi Zelphir,
>> 
>> On Sunday, April 17th, 2022 at 10:49 AM, Zelphir Kaltstahl 
>> <zelphirkaltstahl@posteo.de> wrote:
>> 
>>> I have the same indentation issue though, when I use #||# comments 
>>> for
>>> arguments, which are not keyword arguments, but I want to hint what 
>>> they are
>>> used for. One could argue, that I should rewrite the called function 
>>> to use
>>> keyword arguments, or, if it is a library function, I should wrap it. 
>>> Hmmm.
>>> Maybe that's a valid point.
>> Or document the function and its parameter using a documentation 
>> string (docstring) instead of comments? This way, you or the users of 
>> your code can read that documentation with Emacs Geiser.
>> 
>> For instance:
>> 
>> (define (get-field record field)
>>    "Get the value of FIELD from RECORD.
>> 
>>    RECORD (Guile Record or SRFI 9 Record)
>>      A record of any type.
>> 
>>    FIELD (Symbol)
>>      The name of the field.
>> 
>>    RETURN VALUE (Anything)
>>      The value of the field.
>> 
>>    If the FIELD does not exist, a no-such-field exception is raised."
>>    (let* [(descriptor (record-type-descriptor record))
>>           (access-field (record-accessor descriptor field))]
>> 
>>      (access-field record)))
>> 
>> Then, in Emacs, when calling this procedure, you would place the caret 
>> in get-field, press C-c C-d C-d, and Emacs would show its 
>> documentation in a buffer.
>> 
>> That's my documentation style, though, which is not conventional, but 
>> just an example.
>> 
>> Using documentation string is also useful if you later want to 
>> [auto]generate API documentation.
> 
> It is a good idea to document ones code, of course, even for future 
> self : )
> 
> Usually when I `M-x run-geiser RET` or `M-x run-geiser RET` and then
> move the cursor into a function call and the function is somehow
> available to Geiser, I see a line at the bottom of my Emacs, which
> lists the arguments and highlights the argument, which I should be
> filling in next. That is already very helpful.
> 
> However, this is all assuming, that everyone uses Emacs. Comments
> would be more universally accessible. (I know it sounds almost crazy
> not to use Emacs for coding Guile ;D) That would help others, who do
> not use Emacs as well.
> 
> I like the documentation style in the doc string you are proposing.
> Not sure I will always go to that length myself, but it would probably
> be a good practice. Just like you said, for generating auto-generating
> things like API docs. Btw.: What is the standard tool in the Guile
> ecosystem to do that from doc strings like yours?
> 
> Also thanks for the C-c C-d C-d hint. I did not know the shortcut.
> 
> Best regards,
> Zelphir



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-18 10:48       ` Zelphir Kaltstahl
  2022-04-18 13:33         ` Ricardo G. Herdt
@ 2022-04-18 14:05         ` Luis Felipe
  1 sibling, 0 replies; 12+ messages in thread
From: Luis Felipe @ 2022-04-18 14:05 UTC (permalink / raw)
  To: Zelphir Kaltstahl; +Cc: guile-user


[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]

On Monday, April 18th, 2022 at 10:48 AM, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:

> I like the documentation style in the doc string you are proposing. Not sure I
> will always go to that length myself, but it would probably be a good practice.
> Just like you said, for generating auto-generating things like API docs. Btw.:
> What is the standard tool in the Guile ecosystem to do that from doc strings
> like yours?

None that I know of :)

But I see there are pieces around that could make it possible to generate documentation [semi]automatically:

+ procedure-documentation
  (https://www.gnu.org/software/guile/manual/guile.html#Procedure-Properties)

+ (scheme documentation) module from guile-lib
  (https://www.nongnu.org/guile-lib/doc/ref/scheme.documentation/)

+ (ice-9 documentation) module
  (https://git.savannah.gnu.org/cgit/guile.git/tree/module/ice-9/documentation.scm)

+ guild doc-snarf command
  (although this one doesn't generate any output when passing a module with docstrings)


> Also thanks for the C-c C-d C-d hint. I did not know the shortcut.

You're welcome :)

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: Indentation with inline comments in Emacs
  2022-04-18 13:33         ` Ricardo G. Herdt
@ 2022-04-18 14:09           ` Luis Felipe
  0 siblings, 0 replies; 12+ messages in thread
From: Luis Felipe @ 2022-04-18 14:09 UTC (permalink / raw)
  To: Ricardo G. Herdt; +Cc: guile-user


[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]

On Monday, April 18th, 2022 at 1:33 PM, Ricardo G. Herdt <r.herdt@posteo.de> wrote:

> actually the doc-strings are available during runtime using '(ice-9
> documentation)', so theoretically it is not restricted to Emacs. In fact
> I have been working on my spare time on a LSP server for scheme
> (together with a emacs-lsp and a VS Code extension), and documentation
> of guile functions was quite straight-forward to implement. It's not yet
> ready for prime time though.

That sounds great.

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2022-04-18 14:09 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-16 12:12 Indentation with inline comments in Emacs Zelphir Kaltstahl
2022-04-16 14:57 ` Jérémy Korwin-Zmijowski
2022-04-17 10:49   ` Zelphir Kaltstahl
2022-04-17 13:44     ` Luis Felipe
2022-04-18 10:48       ` Zelphir Kaltstahl
2022-04-18 13:33         ` Ricardo G. Herdt
2022-04-18 14:09           ` Luis Felipe
2022-04-18 14:05         ` Luis Felipe
2022-04-17  3:03 ` Taylan Kammer
2022-04-17 11:06   ` Zelphir Kaltstahl
2022-04-17 14:58     ` Maxime Devos
2022-04-18 10:49       ` Zelphir Kaltstahl

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).