Skip to content

Commit 757677e

Browse files
moppmopp
committed
feat: add session information
1 parent 2c9b06e commit 757677e

File tree

10 files changed

+203
-0
lines changed

10 files changed

+203
-0
lines changed

‎2025/src/content/sessions/atusy.toml‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
session_id = "atusy"
2+
start_at = 2025-11-02T14:20:00+09:00
3+
end_at = 2025-11-02T14:50:00+09:00
4+
speaker_name = "atusy"
5+
title = 'Beyond Syntax Highlighting: Unlocking the Power of Tree-sitter in Neovim'
6+
abstract = '''
7+
Neovim users get benefits of beautiful syntax highlighting with Tree-sitter.
8+
However, Tree-sitter can do much more than just syntax highlighting.
9+
Once you understand it is actually an incremental parsing library, you may come up with various ways to enhance your text edit experience.
10+
11+
I will introduce some of my favorite use cases and their implementations (tree-sitter parser, query, and Neovim plugin).
12+
Audience can try out these examples themselves, or use them as a starting point for their own creative ideas.
13+
14+
Here are some of the use cases I will cover:
15+
16+
* Select and edit syntactically meaningful regions
17+
* select a specific kind of nodes as text objects (e.g. function, class, etc.)
18+
* select a node that includes the cursor position with a help of easymotion-like labelling
19+
* Add extra highights to your code
20+
* change the background color of code blocks in markdown files
21+
* emphasize URL paths in literal string
22+
* and more
23+
* syntax-aware code folding
24+
* context-aware key mappings based on the node under the cursor
25+
26+
Also, I would like to introduce `treesitter-ls`, a tree-sittere-powered language server.
27+
Although this is currently a work in progress, it is worth introducing as it potentially provides the power of tree-sitter to non-Neovim users.
28+
'''

‎2025/src/content/sessions/hrsh7th.toml‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
session_id = "hrsh7th"
2+
start_at = 2025-11-02T10:00:00+09:00
3+
end_at = 2025-11-02T10:50:00+09:00
4+
speaker_name = "hrsh7th"
5+
title = 'nvim-cmp retrospective: Exploring Completion and Facing FOSS Challenges'
6+
abstract = '''
7+
Over 15 years with Vim, I transitioned from user to OSS contributor and plugin creator.
8+
This keynote reflects on my nvim-cmp journey, sharing insights into text completion across Vim, VSCode, and LSP.
9+
Meanwhile, I'll candidly discuss FOSS challenges—maintenance limits and burnout—touching on my current perspectives.
10+
'''
11+
self_introduction = '''
12+
hrsh7th is a Web frontend engineer based in Japan.
13+
With around 15 years of experience using (n)vim, he's the author of popular plugins like vim-vsnip and nvim-cmp.
14+
As a Web frontend engineer, he has a strong interest in enhancing editor-based workflows and user experience for daily development.
15+
'''

‎2025/src/content/sessions/kawarimidoll.toml‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
session_id = "kawarimidoll"
2+
start_at = 2025-11-02T13:15:00+09:00
3+
end_at = 2025-11-02T13:35:00+09:00
4+
speaker_name = "kawarimidoll"
5+
title = 'Getting Started with *your own* Neovim feat. mini.nvim'
6+
abstract = '''
7+
It's exciting to start using Neovim with the thought, "Using Neovim is cool!"
8+
Many beginners want to improve their Neovim. They often start by copying settings recommended on websites or YouTube.
9+
That's fine and can be useful, but it's still using someone else's Neovim as long as you're just following recommendations.
10+
To truly make Neovim your own, you need to understand what you can achieve by configuring it yourself.
11+
Many beginners simply don't know what's possible through configuration. That's why I'll introduce some of those possibilities.
12+
In this talk, I'll show you an overview of Neovim features and settings using a nice plugin, mini.nvim.
13+
This plugin is a collection of many useful modules that you can mix and match according to your needs.
14+
By exploring these modules, you'll gain insight into what Neovim can do and what features you might need.
15+
More importantly, you'll learn to think about what you want to achieve, how to figure out the best way to do it, and how to write the right settings for that.
16+
This process helps you develop your engineering skills.
17+
You'll also experience the joy of growing your configuration. It's not just useful, it's really fun!
18+
Let's get started with your own Neovim, featuring mini.nvim!
19+
Disclaimer: I'm not the author of mini.nvim. I'm a big fan of it and use it in my Neovim configuration.
20+
'''

‎2025/src/content/sessions/kuuote.toml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
session_id = "kuuote"
2+
start_at = 2025-11-02T14:50:00+09:00
3+
end_at = 2025-11-02T15:20:00+09:00
4+
speaker_name = "kuuote"
5+
title = 'Assists text writing anywhere'
6+
abstract = '''
7+
In recent years, the rise of generative AI has only heightened the importance of writing skills. In this presentation, I'll explain how Vim's rich editing features make it particularly suitable for writing, and how customization can enhance your writing experience. I'll demonstrate this with practical examples from my own workflow, then share my method for quickly exporting text outside of Vim.
8+
'''

‎2025/src/content/sessions/mikoto2000.toml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
session_id = 'mikoto2000'
2+
start_at = 2025-11-02T15:35:00+09:00
3+
end_at = 2025-11-02T15:55:00+09:00
4+
speaker_name = 'mikoto2000'
5+
title = 'Cloud-Native, but Still Want to Use Vim: Running Vim Editor in Eclipse Che IDE'
6+
abstract = '''
7+
Vimmers are the kind of people who want to use Vim anytime, anywhere — and that doesn’t change even in a cloud-native world.
8+
I’ve been working on a way to run the Vim editor inside Eclipse Che, a cloud-native IDE.
9+
It’s not fully production-ready yet, but in this talk, I’d like to share how it works and discuss the challenges I’ve faced.
10+
'''

‎2025/src/content/sessions/rbtnn.toml‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
session_id = "rbtnn"
2+
start_at = 2025-11-02T11:00:00+09:00
3+
end_at = 2025-11-02T11:50:00+09:00
4+
speaker_name = "rbtnn"
5+
title = 'WIP'
6+
abstract = '''
7+
WIP
8+
'''
9+
self_introduction = '''
10+
rbtnn is what you might call an SIer in Japan. These days, his main role is team management, so he doesn't get to write code as often.
11+
That said, he worked across the stack throughout his career—from server-side and client-side development to embedded systems—making him a so-called full-stack engineer.
12+
Vim has been his primary text editor for nearly 15 years, and he uses it to write code in almost any programming language.
13+
He's contributed to Vim itself several times in the past, and this time, He'd like to introduce a feature he implemented called TabPanel, and share the background and motivation behind adding it.
14+
'''

‎2025/src/content/sessions/satoru_kitaguchi_dot.toml‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
session_id = "satoru_kitaguchi_dot"
2+
start_at = 2025-11-02T15:55:00+09:00
3+
end_at = 2025-11-02T16:15:00+09:00
4+
speaker_name = "Satoru Kitaguchi"
5+
title = 'Designing Repeatable Edits: The Architecture of . in Vim'
6+
abstract = '''
7+
Vim’s dot (.) command is deceptively simple—it repeats the last change.
8+
But beneath this minimalism lies one of Vim’s most powerful ideas: editing as a repeatable, structured action.
9+
Dot doesn’t just replay—it expresses Vim’s philosophy of reusable, composable editing.
10+
11+
In this session, we’ll explore how dot works under the hood: how edits are recorded and replayed, and why some actions are repeatable while others are not.
12+
We'll then move into practical techniques for designing dot-friendly edits using operators, motions, and text objects.
13+
14+
We’ll also look at why many plugin actions don’t support dot repeat by default, and how tools like repeat.vim and repeat#set() help restore consistency.
15+
By understanding how to align plugin behavior with Vim’s model, we can extend dot’s elegance even in custom workflows.
16+
17+
Ultimately, this talk is not just about using . more effectively—it’s about writing edits and workflows that align with it, unlocking a deeper level of speed, clarity, and composability in your Vim usage.
18+
'''

‎2025/src/content/sessions/satoru_kitaguchi_register.toml‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
session_id = "satoru_kitaguchi_register"
2+
start_at = 2025-11-02T16:15:00+09:00
3+
end_at = 2025-11-02T16:35:00+09:00
4+
speaker_name = "Satoru Kitaguchi"
5+
title = "You Know They're Not Just Clipboards — Now Learn What They Really Are"
6+
abstract = '''
7+
You already know Vim registers aren’t just clipboards.
8+
But when asked:
9+
“Why didn’t it go into ""0""?”,
10+
“What’s rotating in ""1–9""?”,
11+
or “Why did the thing I just copied disappear?” —
12+
can you explain why?
13+
14+
Vim’s register system is both powerful and subtle.
15+
It tracks what gets saved, when it's overwritten, and which register each operation touches—often silently.
16+
Understanding this system is key to avoiding accidental loss and enabling intentional, reusable editing workflows.
17+
18+
In this talk, we’ll break down how each register works: ""0"", ""1–9"", ""a–z"", ""="", ""_"", ""*"" and others.
19+
You’ll learn practical techniques for designing safer edits, preserving state, and even injecting dynamic content from expressions or shell commands.
20+
21+
This session will help you stop guessing—and start thinking in registers.
22+
'''

‎2025/src/content/sessions/teppei22.toml‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
session_id = "teppei22"
2+
start_at = 2025-11-02T13:00:00+09:00
3+
end_at = 2025-11-02T13:15:00+09:00
4+
speaker_name = "teppei22"
5+
title = 'Lowering the Vim Barrier: Building nvim Environment with AI Assistance'
6+
abstract = '''
7+
As a vim beginner, I've always felt the steep learning curve of vim was intimidating. However, with the advent of AI-powered coding assistants, the barriers to entry for various technologies, including vim, have significantly lowered. This talk explores how AI is democratizing vim adoption.
8+
9+
In this session, I will share:
10+
- My journey from vim-curious to vim user through AI assistance
11+
- How to build nvim configuration with AI guidance step by step
12+
- Essential plugins and configurations for beginners using AI tools
13+
- How to leverage AI to understand complex vim concepts and commands
14+
- Creating beginner-friendly documentation and README.md/CLAUDE.md with AI help
15+
- Common pitfalls and how AI can help avoid them
16+
17+
This talk is aimed at vim-curious developers and beginners who want to overcome the traditional vim learning curve by leveraging modern AI tools to make their Step 0 into the vim world more approachable.
18+
'''

‎2025/src/content/sessions/Λlisue.toml‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
session_id = "Λlisue"
2+
start_at = 2025-11-02T13:35:00+09:00
3+
end_at = 2025-11-02T14:05:00+09:00
4+
speaker_name = "Λlisue"
5+
title = "And Yet, Vim Survived: Thinking and Seeing in the Age of Code You Don't Write"
6+
abstract = '''
7+
In the year 202X, the world was ravaged by AI-assisted coding.
8+
Functions were generated automatically. Code reviews ran on natural language prompts.
9+
Developers stopped writing code and became... prompt engineers.
10+
11+
Text editors disappeared — or so it seemed.
12+
But Vim survived.
13+
14+
I’m no exception.
15+
These days, the first draft of code often comes from an AI, and I rarely need to write loops or simple routines myself.
16+
But while I’m writing less, I’m spending a lot more time reading.
17+
18+
Why is this function written this way?
19+
What role does this design play in the bigger picture?
20+
Who made this change — and why?
21+
22+
Even in an age where machines write the code,
23+
understanding the flow, the structure, and the reasoning still falls to us.
24+
25+
And that’s when I realized:
26+
Vim is absurdly good at seeing.
27+
28+
Split windows for parallel perspectives.
29+
Mode switching to shift context.
30+
Jumps and searches to trace the flow.
31+
Viewing code alongside its history.
32+
Custom mappings to navigate between layers of abstraction.
33+
34+
With tools like Fall, Fern, and Gin,
35+
Vim transforms from just a code editor into a thinking interface.
36+
37+
In this talk, I’ll share why I still use Vim
38+
in a time where writing code is no longer the main act.
39+
40+
As more of our code is machine-generated,
41+
how we look at it — and what we pay attention to — becomes more important.
42+
43+
I’ll walk through how I use Vim to “see,”
44+
through the lens of Fall, Fern, and Gin.
45+
46+
The machine can write.
47+
But I still need to see.
48+
You’re no longer writing.
49+
And yet—you’re still watching.
50+
'''

0 commit comments

Comments
 (0)