New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vimfest 2017 - call for speakers #3

Closed
wikimatze opened this Issue Sep 20, 2016 · 30 comments

Comments

Projects
None yet
@wikimatze
Member

wikimatze commented Sep 20, 2016

Please provider your talk proposal in the following format:

## title

## Your name (as well as GitHub + twitter account)

## Abstract

## Approximate length of the talk

Please name the target audience for your talk (e.g. beginner, intermediate, advanced, for everyone).

@blackode

This comment has been minimized.

Show comment
Hide comment
@blackode

blackode Dec 8, 2016

Why I left Vim and came back.

John Ankanna https://github.com/blackode + https://twitter.com/tweetblackode

Sharing Experiences of How I got into vim and reasons for leaving vim and coming back to the gem of editors Vim.The reasons why people leave vim at first and comes back realizing its importance. This all about the ease of vim usage and basic reasons why Vim. The talk will be about what person think first time using the vim and comes back after a while. This gonna be some funny demonstration of vim comparing the basic editors.

15 min

everyone

blackode commented Dec 8, 2016

Why I left Vim and came back.

John Ankanna https://github.com/blackode + https://twitter.com/tweetblackode

Sharing Experiences of How I got into vim and reasons for leaving vim and coming back to the gem of editors Vim.The reasons why people leave vim at first and comes back realizing its importance. This all about the ease of vim usage and basic reasons why Vim. The talk will be about what person think first time using the vim and comes back after a while. This gonna be some funny demonstration of vim comparing the basic editors.

15 min

everyone

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Dec 30, 2016

Member

Thanks @blackode for submitting the first proposal.

Member

wikimatze commented Dec 30, 2016

Thanks @blackode for submitting the first proposal.

@askedrelic

This comment has been minimized.

Show comment
Hide comment
@askedrelic

askedrelic Mar 21, 2017

Title

My theory of VIM the IDE

Author

Matt Behrens
https://twitter.com/askedrelic
https://github.com/askedrelic

Astract

I would like to highlight the abilities that I have assembled, to make Vim a good IDE for any language. These abilities involve easy file searching, grepping, syntax highlighting, and formatting of code to start. Sometimes there is a builtin way to accomplish something, sometimes through finding the right plugin, and sometimes through hacking up some Vimscript. Often, there are multiple ways of accomplishing something and you are free to make the choice. I'd like to share the choices I've made and hopefully improve your experience in VIM.

15m-30m? Should be beginner to intermediate.

askedrelic commented Mar 21, 2017

Title

My theory of VIM the IDE

Author

Matt Behrens
https://twitter.com/askedrelic
https://github.com/askedrelic

Astract

I would like to highlight the abilities that I have assembled, to make Vim a good IDE for any language. These abilities involve easy file searching, grepping, syntax highlighting, and formatting of code to start. Sometimes there is a builtin way to accomplish something, sometimes through finding the right plugin, and sometimes through hacking up some Vimscript. Often, there are multiple ways of accomplishing something and you are free to make the choice. I'd like to share the choices I've made and hopefully improve your experience in VIM.

15m-30m? Should be beginner to intermediate.

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Mar 22, 2017

Member

Hi @askedrelic thanks for your proposal. I like the topic. Do you mind 30 minutes are fine for you? This may include Q&A as well as further questions from the audience.

Member

wikimatze commented Mar 22, 2017

Hi @askedrelic thanks for your proposal. I like the topic. Do you mind 30 minutes are fine for you? This may include Q&A as well as further questions from the audience.

@askedrelic

This comment has been minimized.

Show comment
Hide comment
@askedrelic

askedrelic Mar 23, 2017

@wikimatze sounds good, I will aim for 30m for the presentation. Q&A will be fine.

askedrelic commented Mar 23, 2017

@wikimatze sounds good, I will aim for 30m for the presentation. Q&A will be fine.

@DanielSiepmann

This comment has been minimized.

Show comment
Hide comment
@DanielSiepmann

DanielSiepmann Jun 21, 2017

3 Lightning talks by https://github.com/DanielSiepmann / https://twitter.com/layneobserdia

Writing NeoVim Plugins using Python Plugin API

Abstract

I've written my first NeoVim plugin using the new Plugin API and Python 3, see https://github.com/neovim/python-client .
I can introduce how to write plugins using the new API.

Approximate length of the talk

Round about 10 - 15 Minutes

Python unit testing

Abstract

How to add unit test to your Neovim Python plugin and executing them via https://github.com/janko-m/vim-test inside Neovim.

Approximate length of the talk

Round about 10 - 15 Minutes

Gitlab CI

Abstract

How to integrate Unittests, CGL and Co into Gitlab CI https://gitlab.com/DanielSiepmann/neotags/pipelines .

Approximate length of the talk

Round about 10 - 15 Minutes

DanielSiepmann commented Jun 21, 2017

3 Lightning talks by https://github.com/DanielSiepmann / https://twitter.com/layneobserdia

Writing NeoVim Plugins using Python Plugin API

Abstract

I've written my first NeoVim plugin using the new Plugin API and Python 3, see https://github.com/neovim/python-client .
I can introduce how to write plugins using the new API.

Approximate length of the talk

Round about 10 - 15 Minutes

Python unit testing

Abstract

How to add unit test to your Neovim Python plugin and executing them via https://github.com/janko-m/vim-test inside Neovim.

Approximate length of the talk

Round about 10 - 15 Minutes

Gitlab CI

Abstract

How to integrate Unittests, CGL and Co into Gitlab CI https://gitlab.com/DanielSiepmann/neotags/pipelines .

Approximate length of the talk

Round about 10 - 15 Minutes

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Jun 22, 2017

Member

@DanielSiepmann, I think Writing NeoVim Plugins using Python Plugin API is enough for 30 minutes. integration of test execution via https://github.com/janko-m/vim-test as well as CI via Gitlab https://gitlab.com/DanielSiepmann/neotags/pipelines would be something for our lightning talks section.

Member

wikimatze commented Jun 22, 2017

@DanielSiepmann, I think Writing NeoVim Plugins using Python Plugin API is enough for 30 minutes. integration of test execution via https://github.com/janko-m/vim-test as well as CI via Gitlab https://gitlab.com/DanielSiepmann/neotags/pipelines would be something for our lightning talks section.

@askedrelic

This comment has been minimized.

Show comment
Hide comment
@askedrelic

askedrelic Jun 22, 2017

If anyone is looking for ideas, continuing with the Neovim theme would be great. I just recently got Neovim installed and figured out; I'd feel like a "Neovim in 15 minutes" explaining how to get started from scratch and highlighting the main differences would be interesting.

Alternatively, something like "The State of Neovim" would be interesting, highlighting the recent v0.2 release and how the project is going, if anyone is really watching the repo and can comment!

askedrelic commented Jun 22, 2017

If anyone is looking for ideas, continuing with the Neovim theme would be great. I just recently got Neovim installed and figured out; I'd feel like a "Neovim in 15 minutes" explaining how to get started from scratch and highlighting the main differences would be interesting.

Alternatively, something like "The State of Neovim" would be interesting, highlighting the recent v0.2 release and how the project is going, if anyone is really watching the repo and can comment!

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Jun 22, 2017

Member

@askedrelic great idea, I've switched recently to NeoVim and could also give a talk about it. I'm sure I can ask @justinmk if he would like to give a talk.

Member

wikimatze commented Jun 22, 2017

@askedrelic great idea, I've switched recently to NeoVim and could also give a talk about it. I'm sure I can ask @justinmk if he would like to give a talk.

@DanielSiepmann

This comment has been minimized.

Show comment
Hide comment
@DanielSiepmann

DanielSiepmann Jun 22, 2017

@wikimatze I've updated my comment above and switched to three lightning talks as you've written it makes sense for the second and third topic. Also the plugin API is very effective and therefore small, so there is not much to say or show.

DanielSiepmann commented Jun 22, 2017

@wikimatze I've updated my comment above and switched to three lightning talks as you've written it makes sense for the second and third topic. Also the plugin API is very effective and therefore small, so there is not much to say or show.

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Jun 23, 2017

Member

@DanielSiepmann great. I will consider this on the agenda.

Member

wikimatze commented Jun 23, 2017

@DanielSiepmann great. I will consider this on the agenda.

@justinmk

This comment has been minimized.

Show comment
Hide comment
@justinmk

justinmk Jun 27, 2017

I'll plan to do a neovim talk.

justinmk commented Jun 27, 2017

I'll plan to do a neovim talk.

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Jun 27, 2017

Member

@justinmk That's nice! Think this time we have a bunch more neovim users (including me).

Member

wikimatze commented Jun 27, 2017

@justinmk That's nice! Think this time we have a bunch more neovim users (including me).

@dantleech

This comment has been minimized.

Show comment
Hide comment
@dantleech

dantleech Jun 28, 2017

My Quest for PHP Intellisense

I switched to VIM 10 years ago over that time I have slowly improved my VIM
general configuration while PHP5+ support (intelligent auto-completion
and introspection) has hardly advanced at all. Although there have been many
efforts to address this problem, none of them come very close to providing a
modern IDE experience.

In late 2015 I realised that I had been waiting for years for this
functionality, and that I may as well write something myself - I made my first
attempt, and failed. In June 2017, 4 attempts later, I produced something that
worked.

In this talk I will discuss previous projects which addressed this issue, the
tools that make them possible, present the tool that I have created and other
forthcoming solutions.


Viable PHP Intellisense (autocompletion, introspection) in VIM has long been
sought after, but it may finally be here.

Daniel Leech: Code monkey @inviqa, erstwhile cyclotourist @phpbench @biketourdan

15-30m

dantleech commented Jun 28, 2017

My Quest for PHP Intellisense

I switched to VIM 10 years ago over that time I have slowly improved my VIM
general configuration while PHP5+ support (intelligent auto-completion
and introspection) has hardly advanced at all. Although there have been many
efforts to address this problem, none of them come very close to providing a
modern IDE experience.

In late 2015 I realised that I had been waiting for years for this
functionality, and that I may as well write something myself - I made my first
attempt, and failed. In June 2017, 4 attempts later, I produced something that
worked.

In this talk I will discuss previous projects which addressed this issue, the
tools that make them possible, present the tool that I have created and other
forthcoming solutions.


Viable PHP Intellisense (autocompletion, introspection) in VIM has long been
sought after, but it may finally be here.

Daniel Leech: Code monkey @inviqa, erstwhile cyclotourist @phpbench @biketourdan

15-30m

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Jun 28, 2017

Member

@dantleech thank you very much for your talk.

Member

wikimatze commented Jun 28, 2017

@dantleech thank you very much for your talk.

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Jul 5, 2017

Member

@justinmk do you have a rough title for your talk?

Member

wikimatze commented Jul 5, 2017

@justinmk do you have a rough title for your talk?

@justinmk

This comment has been minimized.

Show comment
Hide comment
@justinmk

justinmk Jul 8, 2017

"Neovim 0.2 features and future"

justinmk commented Jul 8, 2017

"Neovim 0.2 features and future"

@ultimatecoder

This comment has been minimized.

Show comment
Hide comment
@ultimatecoder

ultimatecoder Jul 14, 2017

Head first with vim specific helpfile

Details

Abstract

This talk will provide initial guidelines on writing vim helpfiles. User
documentation is one of the important aspects of any software. Because
vim has a great functionality of dealing helpfile inside the editor, it is very important
to write helpfile accessible inside vim editor and not anywhere else.
Ideally, the talk will cover below points.

  • Discuss the importance of editor specific helpfile.
  • Basics syntax of vim helpfile.
  • How to format your helpfile.
  • Loading any helpfile to your vim editor.
  • Accessing loaded helpfile.
  • Guide on combining helpfile with your plugin so it recognized by plugin
    manager.

Background story

Recently I was trying to observe various vim plugins helpful for writers. Some commonly
suggested goyo. I was shocked to find
that this plugin was not contained any vim specific helpfile. I request the
author to take the responsibility of writing vim specific helpfile for this
plugin, but he didn't agree with that decision at that time reference. I decided to write the helpfile for goyo plugin and wrote goyo-doc. By doing this task I learned the syntax of vim helpfile. I think it is good to discuss the importance of vim specific helpfile with a community and guide them on writing them.

Approximate length: 30 minutes

ultimatecoder commented Jul 14, 2017

Head first with vim specific helpfile

Details

Abstract

This talk will provide initial guidelines on writing vim helpfiles. User
documentation is one of the important aspects of any software. Because
vim has a great functionality of dealing helpfile inside the editor, it is very important
to write helpfile accessible inside vim editor and not anywhere else.
Ideally, the talk will cover below points.

  • Discuss the importance of editor specific helpfile.
  • Basics syntax of vim helpfile.
  • How to format your helpfile.
  • Loading any helpfile to your vim editor.
  • Accessing loaded helpfile.
  • Guide on combining helpfile with your plugin so it recognized by plugin
    manager.

Background story

Recently I was trying to observe various vim plugins helpful for writers. Some commonly
suggested goyo. I was shocked to find
that this plugin was not contained any vim specific helpfile. I request the
author to take the responsibility of writing vim specific helpfile for this
plugin, but he didn't agree with that decision at that time reference. I decided to write the helpfile for goyo plugin and wrote goyo-doc. By doing this task I learned the syntax of vim helpfile. I think it is good to discuss the importance of vim specific helpfile with a community and guide them on writing them.

Approximate length: 30 minutes

@rtorralba

This comment has been minimized.

Show comment
Hide comment
@rtorralba

rtorralba Jul 15, 2017

VIM for PHP developers. The best editor with all IDE features.

Author

Abstract

Everybody knows that VIM is the best and fastest text editor, but some PHP developers change it for other IDEs like PHPStorm, Netbeans...

In this talk we will explain that you can to have the best editor and all necessary features that we must find in a complete IDE at the same time:

File Management

  • Project tree
  • Fuzzy finder file opening
  • Tabs (Buffers)
  • Search and replace
  • Entire project search
  • Syntax checking and highlighting
  • Coding standards checking

Code generation

  • Code completion
  • Snippets
  • Emmet
  • Refactoring
  • PHP use injection and checking
  • Jump to de declaration

GIT integration

  • Fugitive. Awesome GIT operations interface
  • Show changes in file and project tree
  • Advenced GIT browser

Other

  • Debug
  • Bonus track. Useful VIM edition tricks for PHP/Web developers

Approximate length of the talk: 1 hour

rtorralba commented Jul 15, 2017

VIM for PHP developers. The best editor with all IDE features.

Author

Abstract

Everybody knows that VIM is the best and fastest text editor, but some PHP developers change it for other IDEs like PHPStorm, Netbeans...

In this talk we will explain that you can to have the best editor and all necessary features that we must find in a complete IDE at the same time:

File Management

  • Project tree
  • Fuzzy finder file opening
  • Tabs (Buffers)
  • Search and replace
  • Entire project search
  • Syntax checking and highlighting
  • Coding standards checking

Code generation

  • Code completion
  • Snippets
  • Emmet
  • Refactoring
  • PHP use injection and checking
  • Jump to de declaration

GIT integration

  • Fugitive. Awesome GIT operations interface
  • Show changes in file and project tree
  • Advenced GIT browser

Other

  • Debug
  • Bonus track. Useful VIM edition tricks for PHP/Web developers

Approximate length of the talk: 1 hour

@ramonvoges

This comment has been minimized.

Show comment
Hide comment
@ramonvoges

ramonvoges Jul 22, 2017

Neovim – The Historian's Best Friend

Ramon Voges

https://github.com/ramonvoges
https://twitter.com/ramon_voges

Abstract

Historians write a lot of text. A helpful and supportive editor is crucial for their day to day work. In this talk I will introduce some of neo/vim's features and plugins I find most useful while dealing with text. Apart from several vim commands and settings, I will go into detail especially with regard to editing LaTeX and markdown files as well as using git.

Approximate length of the talk

30 min.

Target audience

Beginner and intermediate

ramonvoges commented Jul 22, 2017

Neovim – The Historian's Best Friend

Ramon Voges

https://github.com/ramonvoges
https://twitter.com/ramon_voges

Abstract

Historians write a lot of text. A helpful and supportive editor is crucial for their day to day work. In this talk I will introduce some of neo/vim's features and plugins I find most useful while dealing with text. Apart from several vim commands and settings, I will go into detail especially with regard to editing LaTeX and markdown files as well as using git.

Approximate length of the talk

30 min.

Target audience

Beginner and intermediate

@dubst3pp4

This comment has been minimized.

Show comment
Hide comment
@dubst3pp4

dubst3pp4 Jul 28, 2017

Great proposals so far!
Unfortunately I can't offer a talk but would like to get more into how to configure Vim to support not-yet-or-not-so-good-supported programming languages; which is:

  • how to write syntax files
  • adding tags support (simple etags configuration)
  • basic omni completion
  • enhancing plugins like Syntastic

At the moment I'm figuring this things out for my own for a modern FreePascal / ObjectPascal support. But I have also other languages in mind (like Factor etc.).

dubst3pp4 commented Jul 28, 2017

Great proposals so far!
Unfortunately I can't offer a talk but would like to get more into how to configure Vim to support not-yet-or-not-so-good-supported programming languages; which is:

  • how to write syntax files
  • adding tags support (simple etags configuration)
  • basic omni completion
  • enhancing plugins like Syntastic

At the moment I'm figuring this things out for my own for a modern FreePascal / ObjectPascal support. But I have also other languages in mind (like Factor etc.).

@DanielSiepmann

This comment has been minimized.

Show comment
Hide comment
@DanielSiepmann

DanielSiepmann Jul 28, 2017

Instead of my proposed talks I can talk about how to configure plugins like vim-test for neovim and syntastic to offer support there. Also about tags, just a little bit and also a bit about syntax files, so 15 minutes should be fine to introduce into this topics and where to get more information.

DanielSiepmann commented Jul 28, 2017

Instead of my proposed talks I can talk about how to configure plugins like vim-test for neovim and syntastic to offer support there. Also about tags, just a little bit and also a bit about syntax files, so 15 minutes should be fine to introduce into this topics and where to get more information.

@dubst3pp4

This comment has been minimized.

Show comment
Hide comment
@dubst3pp4

dubst3pp4 Jul 28, 2017

@DanielSiepmann oh no but not when we have to renounce your talks! ;-)

dubst3pp4 commented Jul 28, 2017

@DanielSiepmann oh no but not when we have to renounce your talks! ;-)

@WolfgangMehner

This comment has been minimized.

Show comment
Hide comment
@WolfgangMehner

WolfgangMehner Jul 31, 2017

Vim Mapathon - An advanced introduction to maps

Wolfgang Mehner

GitHub

Abstract

I will highlight some of the more advanced uses of maps:

  • Extending maps with expressions and VimScript
  • Maps for the Vim command-line
  • A short digression on custom completion for ex-commands (using tab) [*]
  • Custom completion on the command-line using maps (e.g. CTRL+P style completion)
  • Putting it all together to make your plug-ins (in lack of a better word) sparkle [*]

With a bit of effort and a few recurring tricks you can match or even improve upon the comfort the command-line completion your shell offers. Authors of plug-ins will hopefully find some interesting suggestions, but normal users of Vim can improve their workflow as well.

I can do 15 min, but I can also go a bit longer, for [*]

WolfgangMehner commented Jul 31, 2017

Vim Mapathon - An advanced introduction to maps

Wolfgang Mehner

GitHub

Abstract

I will highlight some of the more advanced uses of maps:

  • Extending maps with expressions and VimScript
  • Maps for the Vim command-line
  • A short digression on custom completion for ex-commands (using tab) [*]
  • Custom completion on the command-line using maps (e.g. CTRL+P style completion)
  • Putting it all together to make your plug-ins (in lack of a better word) sparkle [*]

With a bit of effort and a few recurring tricks you can match or even improve upon the comfort the command-line completion your shell offers. Authors of plug-ins will hopefully find some interesting suggestions, but normal users of Vim can improve their workflow as well.

I can do 15 min, but I can also go a bit longer, for [*]

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Aug 1, 2017

Member

@dubst3pp4, your questions are good topics for short ready and small try errors.
@DanielSiepmann you don't need to change your proposals, we will just keep them.

Member

wikimatze commented Aug 1, 2017

@dubst3pp4, your questions are good topics for short ready and small try errors.
@DanielSiepmann you don't need to change your proposals, we will just keep them.

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Aug 1, 2017

Member

@WolfgangMehner, thanks for your proposal. I'll schedule around 45 minutes for your talk. I think there will be many questions from the audience.

Member

wikimatze commented Aug 1, 2017

@WolfgangMehner, thanks for your proposal. I'll schedule around 45 minutes for your talk. I think there will be many questions from the audience.

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Sep 9, 2017

Member

@dubst3pp4 I'll put you in the lighting topic section then.
@DanielSiepmann

 I can talk about how to configure plugins like vim-test for neovim and syntastic to offer support there. Also about tags, just a little bit and also a bit about syntax files, so 15 minutes should be fine to introduce into this topics and where to get more information.

This is also fine for lightning talks section for the day.

Member

wikimatze commented Sep 9, 2017

@dubst3pp4 I'll put you in the lighting topic section then.
@DanielSiepmann

 I can talk about how to configure plugins like vim-test for neovim and syntastic to offer support there. Also about tags, just a little bit and also a bit about syntax files, so 15 minutes should be fine to introduce into this topics and where to get more information.

This is also fine for lightning talks section for the day.

@wikimatze wikimatze closed this Sep 9, 2017

@dubst3pp4

This comment has been minimized.

Show comment
Hide comment
@dubst3pp4

dubst3pp4 Sep 9, 2017

@wikimatze I had a little shock that I'm listed as speaker. I don't think that I can contribute something interesting, I'm just curious if others have tips in creating language support in Vim ;-)

dubst3pp4 commented Sep 9, 2017

@wikimatze I had a little shock that I'm listed as speaker. I don't think that I can contribute something interesting, I'm just curious if others have tips in creating language support in Vim ;-)

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Sep 9, 2017

Member

@dubst3pp4 why not give a small report about how far you get withmodern FreePascal / ObjectPascal support? I'll remove you from the speakers list then so far and put you instead in the QA section. Would that be okay?

Member

wikimatze commented Sep 9, 2017

@dubst3pp4 why not give a small report about how far you get withmodern FreePascal / ObjectPascal support? I'll remove you from the speakers list then so far and put you instead in the QA section. Would that be okay?

@wikimatze

This comment has been minimized.

Show comment
Hide comment
@wikimatze

wikimatze Sep 24, 2017

Member

Thanks for all the great talks, they made Vimfest 2017 just awesome.

Member

wikimatze commented Sep 24, 2017

Thanks for all the great talks, they made Vimfest 2017 just awesome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment