Starting of the Documentation #1961

TornaxO7 · 2021-02-16T09:45:17Z

Currently added

Added Table of Contents in the CONTRIBUTE.md file
Added new section: 'Documentation'
=> Added a little file structure

Information

The documentation isn't finished yet! I'll tell you if it's finished. I just wanted to start the pull request, so you can see "live" each commit and be able to review it immediately. I thought, that it might suit, if I ask some question here, instead of creating a new issue everytime. So "all" questions about the code will be here. Is that okay for you?

- Added Table of Contents in the CONTRIBUTE.md file - Added new section: 'Documentation' => Added a little file structure

TornaxO7 · 2021-02-16T09:47:20Z

Codequestion

So here comes the first question: In your vimtex#options#init() you're calling a lot of init-script-functions. Did you wrote them all at a specifique file or do I have to find them on my own? Because otherwise I'm gonna use grep to find each implementation of the function xD

EDIT
Oh wait. I'm dumb, the functions are written below the vimtex#options#init() function.... sorry! My mistake.

- Started description of the vimtex#init() function.

TornaxO7 · 2021-02-16T10:06:54Z

Hmm.... I'm not sure, but if I continue like that, the documentation might be too detailed (I think). What do you think @lervag ? Because I think that it's easy to understand, what the vimtex#options#init() function does. So one to 3 sentences should be fine.

lervag · 2021-02-18T22:05:41Z

I thought, that it might suit, if I ask some question here, instead of creating a new issue everytime. So "all" questions about the code will be here. Is that okay for you?

Yes, that's sensible, thanks!

Hmm.... I'm not sure, but if I continue like that, the documentation might be too detailed (I think). What do you think @lervag?

Yes, I think so too. I think one should aim for more or less self-documented code (although that is of course very hard). Avoid too many side effects, use good variable and function names, consistent styles, and so on. And if needed, one should comment things within the code of course.

I think the extra documentation we are discussing now should focus more on the structure and "architecture" than on the detailed level of the code. But still, I do see clear value in making the code more available through some high-level documentation, so thanks for starting this work!

CONTRIBUTING.md

lervag · 2021-02-18T22:09:40Z

CONTRIBUTING.md

+│   └── tex.vim
+├── test
+└── xclip
+```


The problem with adding a listing like this is that it quickly becomes out-of-date because I (and other contributors) will forget to update it. Do we really need to list all of this?

What's the main intent? Perhaps the structure? How about taking it one step back and instead explain the intent of the directories themselves, and not the individual files? We can point the user to the relevant sections in the vim help docs (e.g. :help autoload, :help ftdetect, etc).

The problem with adding a listing like this is that it quickly becomes out-of-date because I (and other contributors) will forget to update it. Do we really need to list all of this?

You're right. I've got another idea: Let's create a table of contents, which should represent the directory-structure of VimTex. So if someone VimTex/autoload/vimtex/compiler, than he/she just needs to click on this path in the TOC and gets a short description about the directory.

How about taking it one step back and instead explain the intent of the directories themselves, and not the individual files?

Aye!

We can point the user to the relevant sections in the vim help docs (e.g. :help autoload, :help ftdetect, etc).

Yes, I'd also like to add a link to this awesome book which taught me vimscript ;)

You're right. I've got another idea: Let's create a table of contents, which should represent the directory-structure of VimTex. So if someone VimTex/autoload/vimtex/compiler, than he/she just needs to click on this path in the TOC and gets a short description about the directory.

I'm not sure I fully understand... "So if someone VimTex/autoload/vimtex/compiler" - I think you forgot a verb in the sentence...?

Yes, I'd also like to add a link to this awesome book which taught me vimscript ;)

Yes, feel free to add a link in the code documentation resource. I agree it is a good resource!

lervag · 2021-02-18T22:10:13Z

CONTRIBUTING.md

+```
+So how does vimtex start? Well, it calls the `vimtex#init()` function at the
+beginning, if you open a `tex` or a `bib` file (see in `ftplugin`). So let's
+take a look, how vimtex initialises:


I propose to make initialization into a sub section.

lervag · 2021-02-18T22:13:05Z

CONTRIBUTING.md

+       use the color of a vim-error-msg for all vimtex errors).
+    2. Warn the user, if he/she is using deprecated settings
+    3. Save the settings of vimtex which are provided from the user or load its
+       default values (like `g:vimtex_compiler_enabled`)


I think this is going in the right direction. The vimtex#options#init() is made available like this because I realized I sometimes needed it even when not really loading the full plugin (e.g. if you only want the syntax highlighting part).

I think I would say that setting the options are the main part and should be number 1 here, while defining highlight groups is "less important". Also, it is important to use correct names here: there is no such thing as vim-error-msg. There is a group called VimtexError, though.

lervag · 2021-02-18T22:13:28Z

CONTRIBUTING.md

+├── test
+└── xclip
+```
+So how does vimtex start? Well, it calls the `vimtex#init()` function at the


Please note that the plugin should be referred to as VimTeX (see latest release notes). :)

- Added new file: DOCUMENTATION.md

TornaxO7 · 2021-02-23T08:05:41Z

Ok, I added the DOCUMENTATION.md.

I'm not sure I fully understand... "So if someone VimTex/autoload/vimtex/compiler" - I think you forgot a verb in the sentence...?

The table of contents represents what I meant and you're right, I meant So if someone wants to know something about vimtex/autoad/vimtex/compiler, but I forgot the other half of my sentence xD.

TornaxO7 · 2021-02-23T08:09:56Z

Oh no, I did git fetch before to be up to date (I thought that it wouldn't be bad, if I would do that ._.). Should I create a new pull request/branch or it fine for you (or do you have an idea, how I can fix that?)?.

lervag · 2021-02-24T07:31:12Z

Oh no, I did git fetch before to be up to date (I thought that it wouldn't be bad, if I would do that ._.). Should I create a new pull request/branch or it fine for you (or do you have an idea, how I can fix that?)?.

I don't think it matters too much while developing. We can fix the Git tree
after.

If you want to stay on top of master, then you should probably use git fetch, then git rebase master. Try to keep your commits in a single "thread". This often means you need to do a force push if you want to move your work on top of master - I'm perfectly fine with that.

The main drawback of "messy" commits is that I won't merge that "as is" - I might squash it or clean it up myself before merge. This might change the commit author metadata as a consequence. :\

Soo, to conclude: feel free to do as you want. As long as the suggested changes between the PR and the master branch reflect what you want, I'm happy.

In your last version, there seems to be a lot of new html files. Was that on purpose?

…pasted it here.

TornaxO7 · 2021-02-24T08:31:45Z

In your last version, there seems to be a lot of new html files. Was that on purpose?

No it wasn't. I thought that this directory came up, when I executed git fetch but after taking a look into this directory I think that I paste it from somewhere. I removed it now.

- after/ftplugin - autoload/health

TornaxO7 · 2021-02-25T09:06:55Z

Ok, I've got a question about the vimtex/autoload/unite/sources: I saw that it's doing something with the table of contents. So if I've understood it right, vimtex/autoload/unite/sources/vimtex.vim has some functions, which are used to generate the TOC (if we use the :VimtexTocOpen command)?

lervag · 2021-02-25T09:38:59Z

Ok, I've got a question about the vimtex/autoload/unite/sources: I saw that it's doing something with the table of contents. So if I've understood it right, vimtex/autoload/unite/sources/vimtex.vim has some functions, which are used to generate the TOC (if we use the :VimtexTocOpen command)?

This file is there to add the ToC unite source, see :help vimtex-unite (which is part of the vimtex-toc section). I don't think it needs much more explanation, except perhaps a like to the unite repo?

TornaxO7 · 2021-02-25T13:44:05Z

Question [SOLVED]

What's the usage of autoad/vimtex/cache.vim?

lervag · 2021-02-25T13:49:04Z

What's the usage of autoad/vimtex/cache.vim?

Well, caching..?

It defines a set of functions that make it quite easy to create and uses caches, both persistent and non-persistent caches. This is very useful to speed some types of things up, e.g. calls to kpsewhich.

TornaxO7 · 2021-02-25T14:40:30Z

to create and uses caches, both persistent and non-persistent caches.

This information is what I needed! Thank you :)

Question [SOLVED]

What is the main usage for autoload/vimtex/delim.vim?

lervag · 2021-02-28T22:40:09Z

This information is what I needed! Thank you :)

My pleasure :)

What is the main usage for autoload/vimtex/delim.vim?

A couple of things:

It specifies an API for parsing various types of delimiters, as well as some "actions" on delimiters.

The ...#init_buffer() function is called when a VimTeX buffer is loaded and defines e.g. the <plug>(vimtex-delim...) mappings that are mapped to functions. E.g. <plug>(vimtex-delim-toggle-modifier) which does ...#toggle_modifier. The <plug> mappings are given default "targets" in the function s:init_default_mappings in autoload/vimtex.vim, see e.g. here:

vimtex/autoload/vimtex.vim

Lines 141 to 147 in d99f8ff

    
           call s:map(1, 'n', 'dsd', '<plug>(vimtex-delim-delete)') 
        
           call s:map(1, 'n', 'csd', '<plug>(vimtex-delim-change-math)') 
        
           call s:map(1, 'n', 'tsd', '<plug>(vimtex-delim-toggle-modifier)') 
        
           call s:map(1, 'x', 'tsd', '<plug>(vimtex-delim-toggle-modifier)') 
        
           call s:map(1, 'n', 'tsD', '<plug>(vimtex-delim-toggle-modifier-reverse)') 
        
           call s:map(1, 'x', 'tsD', '<plug>(vimtex-delim-toggle-modifier-reverse)') 
        
           call s:map(1, 'i', ']]',  '<plug>(vimtex-delim-close)')

Note that #init_buffer() is found in several files. See the function s:init_buffer in autoload/vimtex.vim: it loads the init_buffer() function in every file where it exists. This gives an interface to easily add new "modules" with new features to VimTeX.

lervag · 2021-03-07T11:46:36Z

I realize this recent answer can be useful to you here as well: #1981 (comment)

(accidentally).

TornaxO7 · 2021-03-07T14:48:26Z

I don't really know where the latex directory came from. So I just removed it since it looks like that it was from me (sorry).

TornaxO7 · 2021-03-07T14:50:50Z

Question [SOLVED]

I went through the debug.vim file. As far as I understood, it should create the stacktrace for the quickfix window. Now I'm unsure what kind of errors it uses. Does it fill the quickfix entries with the errors which come up from a LaTeX-Compiler or does it create the entries from vim itself? For example if you called an unknown function?

…sure what to add more.

lervag · 2021-03-07T20:00:48Z

I went through the debug.vim file. As far as I understood, it should create the stacktrace for the quickfix window.

Yes and no. It creates a stacktrace and allows to pass it to the quickfix window if there is an argument. That is, if you call it with any argument (regardless of how many and what they are), the stacktrace is inserted into the quickfix window. If not, then it only returns the stacktrace as a list.

Now I'm unsure what kind of errors it uses. Does it fill the quickfix entries with the errors which come up from a LaTeX-Compiler or does it create the entries from vim itself? For example if you called an unknown function?

This is internal debugging and is not related to LaTeX at all. What it does it that it parses the stacktrace from the v:throwpoint variable (see :h ...). If this does not exist, then we forcibly create it and remove the top element. It uses a couple of internal mechanisms to attempt to decipher the script local names (i.e. the s: in function! s:myfunc is appointed an internal number).

It should be quite easy to test it: just add call vimtex#debug#stacktrace(1) in some part of VimTeX that is loaded and see how it loads the trace into the quickfix list when you open a tex file.

TornaxO7 · 2021-03-10T13:23:24Z

It should be quite easy to test it: just add call vimtex#debug#stacktrace(1) in some part of VimTeX that is loaded and see how it loads the trace into the quickfix list when you open a tex file.

I'm getting this from the quickfix list:

Am I doing it correctly or why isn't there anything in the list?

TornaxO7 · 2021-03-10T13:29:47Z

Question [SOLVED]

What is the purpose of vimtex/autoload/vimtex/context/cite.vim? vim-language-server can't find any references to the autoload-function vimtex#context#cite#new.

lervag · 2021-03-10T13:31:31Z

Try this:

function! Test() abort
  try
    throw "oops"
  catch
    call vimtex#debug#stacktrace(1)
  endtry
endfunction

TornaxO7 · 2021-03-10T13:47:17Z

Question [SOLVED]

What's the purpose of vimtex/autoload/vimtex/parser/vimcomplete.bst? It looks like a snippet file for me.

lervag · 2021-03-10T14:20:15Z

What is the purpose of vimtex/autoload/vimtex/context/cite.vim? vim-language-server can't find any references to the autoload-function vimtex#context#cite#new.

It provides the citation context for the context menu, see vimtex/autoload/vimtex/context.vim. The latter automatically finds all context entries (currently, only cite.vim exists) and loads them.

See vimtex#contex#init_state. The s:handlers variable is defined at the script level and is a list of all files under context/*.vim, so you see the vimtex#context#{l:handler}#new() will be called with l:hander = 'cite'.

The same or a similar mechanism is used other places as well, e.g.

for the state initialization in vimtex#state#init() -> s:vimtex.new(...) with calls to vimtex#{l:mod}#init_state.
in vimtex#init() -> s:init_buffer() with the s:modules variable.

What's the purpose of vimtex/autoload/vimtex/parser/vimcomplete.bst? It looks like a snippet file for me.

It is used by parser/bib.vim in the s:parse_with_bibtex() function, which will actually run the bibtex problem with the supplied .bst file in order to convert a .bib file to a .bbl file that is much easier to parse.

- "Completed" the DOCUMENTATION.md file.

`vimtex/autoload/vimtex/parser/vimcomplete.bst`.

TornaxO7 · 2021-03-10T14:59:47Z

Ok so the DOCUMENTATION.md should be finished now. It should provide a rough overview of the plugin. You can start to review it now!

lervag

Thank you, I much appreciate this effort, and I agree this venture will become valuable. I have some comments, I hope you don't mind.

I also propose that I make a revision on top after we settle my comments. I want to clean up the language a little bit and perhaps add some more content/context where needed.

lervag · 2021-03-11T21:17:06Z

CONTRIBUTING.md

@@ -1,5 +1,17 @@
 # Guide for code contributions

+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->


I can see the value of doctoc, but I don't expect this file to change that much, so I would propose to remove the auto update tags.

Hm... but I'd like to let

 (...) 

there because, who know's how this file develops :)

lervag · 2021-03-11T21:18:50Z

CONTRIBUTING.md

+VimTex provides a little high-level [documentation](./DOCUMENTATION.md). It's
+still under development, but it might help you to understand the code better (or
+at least faster). If you have any question about the code, feel free to open a
+new issue!


I propose to simplify this. Instead of a section, just add a short remark in the "Documentation style" section with a reference. Don't comment on the state of DOCUMENTATION.md, because it will change and we might forget to update this file.

lervag · 2021-03-11T21:20:39Z

DOCUMENTATION.md

@@ -0,0 +1,235 @@
+# Documentation
+
+Welcome to the high-level documentation of **VimTex**.


I'm not sure if it is a good idea to highlight VimTeX (note capital X as in TeX). I don't do that in the README file either.

DOCUMENTATION.md

lervag · 2021-03-11T21:32:24Z

DOCUMENTATION.md

+The `p` directory just includes more syntax highlighting rules which are *only*
+loaded if they are needed.
+
+### text_obj


I would use text_obj.vim as the title (and similar throughout) to make it clear that it is not a directory, but a file.

lervag · 2021-03-11T21:32:40Z

DOCUMENTATION.md

+functions like `vimtex#text_obj#envtargets#current` to get the current
+environment where the user is.
+
+### view


view.vim vs the sub modules.

DOCUMENTATION.md

lervag · 2021-03-11T21:36:26Z

DOCUMENTATION.md

+The single file (`cite.vim`) is used for the `vimtex-context-citation` part.
+[Here's](https://github.com/lervag/vimtex/pull/1961#issuecomment-795476750) a more detailed description of what it does and what's it's used for.
+
+### fold


As before: fold.vim > fold/*.vim

lervag · 2021-03-11T21:38:29Z

DOCUMENTATION.md

+
+# test
+This directory includes *all* test cases which have to pass in order to have a
+stable and functional awesome VimTex plugin :) Each directory and filename


Hehe, thanks :)

But let's keep it simple and remove "awesome" and the similey. ;)

…as a little remark in the `Documentation style` section. - Removed a little line of DOCTOC (https://github.com/thlorenz/doctoc)

- Set VimTeX style "bold" to "normal"

…rence to the "Learn Vimscript the Hard Way" book by Steve Losh.

Added a little hint to point out that VimTeX is using the `health.vim` framework for doing the health-checks.

- context.vim - fold.vim - text_obj.vim - view.vim TODO: - parser.vim - qf.vim

- parser.vim - qf.vim

TornaxO7

Oh damn. I didn't wanted to create a "review". I thought that I could response to you messages by clicking on this review button... sorry for doing this mess! ._. You can delete these comments starting from this one if you want (I can't delete them somehow).

TornaxO7 · 2021-03-11T22:15:56Z

CONTRIBUTING.md

@@ -1,5 +1,17 @@
 # Guide for code contributions

+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->


Hm... but I'd like to let

 (...) 

there because, who know's how this file develops :)

TornaxO7 · 2021-03-11T22:20:56Z

CONTRIBUTING.md

+VimTex provides a little high-level [documentation](./DOCUMENTATION.md). It's
+still under development, but it might help you to understand the code better (or
+at least faster). If you have any question about the code, feel free to open a
+new issue!


TornaxO7 · 2021-03-11T22:23:34Z

DOCUMENTATION.md

@@ -0,0 +1,235 @@
+# Documentation
+
+Welcome to the high-level documentation of **VimTex**.


DOCUMENTATION.md

TornaxO7 · 2021-03-11T22:42:47Z

DOCUMENTATION.md

+Here's an example:
+```vim
+function VimTexCacheExample()
+    " create a new cache (if the name doesn't exist yet)


DOCUMENTATION.md

TornaxO7 · 2021-03-11T22:48:29Z

DOCUMENTATION.md

+### debug.vim
+This file is used for interal debugging and is not related to LaTeX at all. It
+parses the stacktrace from the `v:throwpoint` variable (see `:h v:throwpoint`
+        for more information). If this does not exist, then we forcibly create


(Neo)Vim did that automatically for me. I fixed that now.

TornaxO7 · 2021-03-11T22:58:27Z

DOCUMENTATION.md

+This directory includes all glyphs like α and β.
+
+### context
+The single file (`cite.vim`) is used for the `vimtex-context-citation` part.


I'm unsure what to write there instead. Could you do this for me or can you provide me some tipps?

lervag · 2021-03-15T10:44:40Z

Oh damn. I didn't wanted to create a "review". I thought that I could response to you messages by clicking on this review button... sorry for doing this mess! ._. You can delete these comments starting from this one if you want (I can't delete them somehow).

No worries. I'll just respond inline here and look over the updates afterwards.

(Neo)Vim did that automatically for me. I fixed that now.

The context here is, I think, the indendation: I guess you have autoindent and smilar options enabled, perhaps even cindent.

I'm unsure what to write there instead. Could you do this for me or can you provide me some tipps?

Yes, no problem.

refer: #1961

lervag · 2021-03-15T10:58:04Z

Thank you for this, I think it can bring a lot of value! I'll add some commits on top with some updates, and feel free to continue contributing if you have more ideas (either docs or other things)! :)

refer: #1961

lervag · 2021-03-15T14:03:42Z

I've pushed a couple of additional commits on top of this now, and I think it has become quite good. Feel free to suggest more improvements.

Additions:

14b6746

- Added Table of Contents in the CONTRIBUTE.md file - Added new section: 'Documentation' => Added a little file structure

Additions:

28a292a

- Started description of the vimtex#init() function.

lervag reviewed Feb 18, 2021

View reviewed changes

- Removed the documentation section in CONTRIBUTING.md

37079ea

- Added new file: DOCUMENTATION.md

removed the html directory. Probably I misclicked on my keyboard and …

1778c1f

…pasted it here.

TornaxO7 added 2 commits February 24, 2021 09:43

Added description for:

a2843b7

- after/ftplugin - autoload/health

Changed one line in the Documentation section.

da271d8

Added a little explanation to autoload/unite/source.

133558e

Added a documentation to the next sections.

66ddf82

TornaxO7 added 3 commits March 7, 2021 15:42

Added description for the 'delim.vim' and 'cache.vim'.

b4e77b4

Refreshed the TOC.

6a59e1c

Removed the latex directory. Looks like that I pasted it here as well

45be05e

(accidentally).

Added a very small description about the complete directory. I'm not …

feba98a

…sure what to add more.

TornaxO7 added 2 commits March 10, 2021 15:23

- Added some images for the DOCUMENTATION.md file

ad34f7e

- "Completed" the DOCUMENTATION.md file.

Added description to vimtex/autoload/vimtex/context.vim and to

9ddec6f

`vimtex/autoload/vimtex/parser/vimcomplete.bst`.

lervag requested changes Mar 11, 2021

View reviewed changes

TornaxO7 added 13 commits March 11, 2021 23:18

- Removed the Documentation section in CONTRIBUTING.md => Moved it …

dab4804

…as a little remark in the `Documentation style` section. - Removed a little line of DOCTOC (https://github.com/thlorenz/doctoc)

- Changed typo "VimTex" to "VimTeX"

d090c6a

- Set VimTeX style "bold" to "normal"

- Removed the bold-marks from "VimTeX" (didn't work before)

3a4aff8

Change the order of the TOC

e5e6573

Added a reference to :h autoload in the autoload section and a refe…

a721719

…rence to the "Learn Vimscript the Hard Way" book by Steve Losh.

Section health:

b7292da

Added a little hint to point out that VimTeX is using the `health.vim` framework for doing the health-checks.

Added a little description to vimtex/autoload/vimtex.vim.

66d9fae

Added empty line between text paragraphs and code listings.

055b3f0

Set code indentation from 4 spaces to 2

ccc014d

Added description to compiler.vim.

762ff23

Added description to the following files:

4e90554

- context.vim - fold.vim - text_obj.vim - view.vim TODO: - parser.vim - qf.vim

Added description for:

0f27003

- parser.vim - qf.vim

Refreshed TOC

3b6a3dc

TornaxO7 commented Mar 11, 2021

View reviewed changes

lervag added a commit that referenced this pull request Mar 15, 2021

merge: add dev docs

47fa4b7

refer: #1961

lervag closed this Mar 15, 2021

lervag added a commit that referenced this pull request Mar 15, 2021

doc: improved code documentation

93603d6

refer: #1961

		@@ -0,0 +1,235 @@
		# Documentation

		Welcome to the high-level documentation of VimTex.

Starting of the Documentation #1961

Starting of the Documentation #1961

Conversation

TornaxO7 commented Feb 16, 2021

Currently added

Information

TornaxO7 commented Feb 16, 2021 • edited

Codequestion

TornaxO7 commented Feb 16, 2021

lervag commented Feb 18, 2021

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

TornaxO7 commented Feb 23, 2021

TornaxO7 commented Feb 23, 2021

lervag commented Feb 24, 2021

TornaxO7 commented Feb 24, 2021

TornaxO7 commented Feb 25, 2021

lervag commented Feb 25, 2021

TornaxO7 commented Feb 25, 2021 • edited

Question [SOLVED]

lervag commented Feb 25, 2021

TornaxO7 commented Feb 25, 2021 • edited

Question [SOLVED]

lervag commented Feb 28, 2021

lervag commented Mar 7, 2021 • edited

TornaxO7 commented Mar 7, 2021

TornaxO7 commented Mar 7, 2021 • edited

Question [SOLVED]

lervag commented Mar 7, 2021

TornaxO7 commented Mar 10, 2021

TornaxO7 commented Mar 10, 2021 • edited

Question [SOLVED]

lervag commented Mar 10, 2021

TornaxO7 commented Mar 10, 2021 • edited

Question [SOLVED]

lervag commented Mar 10, 2021

TornaxO7 commented Mar 10, 2021

lervag left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

TornaxO7 left a comment • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lervag commented Mar 15, 2021

lervag commented Mar 15, 2021

lervag commented Mar 15, 2021

TornaxO7 commented Feb 16, 2021 •

edited

TornaxO7 commented Feb 25, 2021 •

edited

TornaxO7 commented Feb 25, 2021 •

edited

lervag commented Mar 7, 2021 •

edited

TornaxO7 commented Mar 7, 2021 •

edited

TornaxO7 commented Mar 10, 2021 •

edited

TornaxO7 commented Mar 10, 2021 •

edited

TornaxO7 left a comment •

edited