Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 07 2020 14:07

    fmoralesc on master

    make a note in the readme about… (compare)

  • Jul 07 2020 14:04

    fmoralesc on master

    add licensing terms using vim's… (compare)

  • Jul 07 2020 13:45
    yegappan opened #35
  • Jun 27 2020 08:59
    fmoralesc closed #34
  • Jun 27 2020 05:13
    cxgslegend opened #34
  • Apr 18 2019 10:35
    imbolc closed #33
  • Apr 18 2019 00:46
    imbolc opened #33
  • Apr 09 2018 07:30
    mrbig033 edited #32
  • Apr 09 2018 07:30
    mrbig033 edited #32
  • Apr 09 2018 07:24
    mrbig033 edited #32
  • Apr 09 2018 07:23
    mrbig033 edited #32
  • Apr 09 2018 07:23
    mrbig033 edited #32
  • Apr 09 2018 07:23
    mrbig033 opened #32
  • Sep 15 2016 07:12
    00dani opened #31
  • Jul 15 2016 05:12
    pickfire closed #30
  • Jul 14 2016 21:44

    fmoralesc on master

    disable foldcolumn, and don't u… (compare)

  • Jul 08 2016 04:31
    pickfire opened #30
  • Jan 29 2016 01:34
    Pyrohh closed #21
  • Nov 15 2015 14:49

    fmoralesc on 0.2.1

    (compare)

  • Nov 15 2015 14:43

    fmoralesc on master

    :Tutor should enable syntax and… (compare)

Michael Reed
@mreed1
or maybe just not mention vim at all, as to keep the tutorial straightforward
Alejandro Sanchez
@HiPhish
Funny thing: in terminal Vim it actually does work, I can run a REPL or even a new instance of Vim on top of Vim, it simply hides Vim. So I can type :!lua and get a Lua REPL. I doesn't work in a GUI though, which is what I usually use.
Nah, leave it out, let them figure it out themselves. If you get yourself into a mess you have to get yourself out again on your own.
Michael Reed
@mreed1
I can't tell if you're being sarcastic for the second point.
limitations of text and whatnot...
Alejandro Sanchez
@HiPhish
No, I'm not. I thought originally it was a nice piece of trivia to try out, but the tutorial is already large enough. Besides, if you know how to quit Vim, which you should if you have been following the tutorial, then you also know how to quite a Vim inside a Vim.
Michael Reed
@mreed1
okey, sounds good
by the way, I bet if you asked @fmoralesc for commit permissions he might oblige, if you want to of course
I imagine having to go through me or him for all trivial edits is cumbersome
Felipe Morales
@fmoralesc
:+1:
Alejandro Sanchez
@HiPhish
I just tried :!lua in Neovim and it doesn't work that well: the command line keeps growing larger until it covers the screen, just like in MacVim. But Neovim has a terminal emulator, which is better anyway.
I have a bad habit of picking up a project, getting all excited and then dropping off because I have something else to do. If you think giving me commit permissions will make the process more flexible for when I drop off I'm fine with that.
Michael Reed
@mreed1
it's fine, as long as you don't come back after 6 months of inactivity and nuke the repo :grin:
fine with me at least... idk about that other guy
anyways, I'm off. Good night/morning/evening
Felipe Morales
@fmoralesc
"that other guy"... Our Lord you mean, for sure, right?
bb @Pyrohh
Alejandro Sanchez
@HiPhish
OK, I'll try to come up with a summary for chapter 2 then. See you back in a few months ;) Should I delete my forked repo now?
Felipe Morales
@fmoralesc
If you wish ;)
Alejandro Sanchez
@HiPhish
I just did a git clone of the GitHub repository, but when I run git branch it only shows me the master branch, not the tutorial revision branch.
On another note, I would like my name in the credits, but "HiPhish" is a pretty stupid name (not as stupid as XxXDarkDoomMasterXxX but still), and I don't like putting my real name on the internet. Would a pseudonym that looks like a real name be acceptable?
Felipe Morales
@fmoralesc
@HiPhish For the first, you'll probably need to do git fetch -all.
For the second, no problem about it ;)
Florian Walch
@fwalch
@HiPhish FWIW, you can change your GitHub username at https://github.com/settings/admin
Since you don't seem to like it too much :grin:
Alejandro Sanchez
@HiPhish
Nah, my user name is good for an internet name, but not for putting it next to regular names ;)
I ran git fetch --all but I still only see the master branch.
Felipe Morales
@fmoralesc
@HiPhish Now, do git checkout revise-tutorial.
I think the user name is just OK alongside regular names, there isn't a susbtantive difference in my view. It's way better than a throwaway name.
Alejandro Sanchez
@HiPhish
I found it in the meantime, you also have to add the -b flag:
Alejandro Sanchez
@HiPhish
We need to decide on a line length for all tutorials. The default width of a terminal window is 80 characters, but we also have to take into account that a user might have a fold column and line numbers turned on. Should those be hidden when a tutor is being displayed? When you run vimtutor you get an instance of Vim with default settings.
Alejandro Sanchez
@HiPhish
Inline normal commands are highlighted like this: `i`{normal}. Should commands in other modes also have normal like `<esc>`{normal} or should we have insert for that purpose?
Felipe Morales
@fmoralesc
I think it's simpler to have mixed markup: `i{normal}hello<esc>{normal}`.
On the text width issue: yes. I think 72 is a good default for line width.
Alejandro Sanchez
@HiPhish
Backticks get mangled in inline code in Markdown. You need to start and end the inline code with two backticks, then single backticks will be preserved. Otherwise I cannot read what you meant exactly.
72 characters of user-visible text, not actual text, right?
Felipe Morales
@fmoralesc
yes, precisely. 72 chars visible.
`i`{normal}`hello``<esc>`{normal}
(finally!)
Florian Walch
@fwalch
Just because I noticed it while working on a doc PR,:help uses 78 characters.
Felipe Morales
@fmoralesc
The tutor filetype uses the gutter and the foldcolumn (I might remove tha later) so 78 is too wide.
Alejandro Sanchez
@HiPhish
I have started adjusting the width of lines in the first tutorial. Here is how I do it: fire up neovim, create a two vertical windows. One window contains the tutorial with file- and buffer type set to nothing, that way I get the pure text. The other window runs a terminal with its own instance of Neovim. Inside that second Neovim I open up the tutorial as read-only with all default settings.
Then I set :set colorcolumn=73 and :highlight ColorColumn ctermbg=lightgrey guibg=lightgrey in the embedded Neovim to see where to break lines.
Now I can edit the raw tutorial, switch to the formated one, run :e and see the changes.
Alejandro Sanchez
@HiPhish
OK, I'm done with the lines. Commits have been pushed to the repository.
Felipe Morales
@fmoralesc
Thanks a lot, @HiPhish. I was in bed the whole weekend (flu), so I couldn't check it out, but it seems fine ;)
Julio Sueiras
@juliosueiras
sorry to bother(since don't know where else to ask), I am planning to create autocompletion & doc lookup plugin for vim of assembly language(for now is just intel, later ARM and others) using ruby and just want to ask if there is any legal precaution/issues?
Felipe Morales
@fmoralesc
@juliosueiras sorry to read this so so so late!
no, there shouldn't be any issue. why do you think there could be? maybe the texts you are using for doc lookup are copyrighted?