Auto Sequential Filename
approvedby yueyinfeng
Create Markdown files with sequential filenames such as GS0001 and RY0001. - This plugin has not been manually reviewed by Obsidian staff.
Auto Sequential Filename
Auto Sequential Filename is an Obsidian plugin that creates Markdown files with sequential filenames, such as GS0001.md, GS0002.md, or RY0001.md.
这个插件适合为固定文件夹自动创建带顺序编号的笔记,例如公司列表、人员列表、项目档案等。
Current release target: desktop Obsidian. Mobile support has not been verified yet.
Features
- Configure multiple target folders.
- Use a different filename prefix for each folder.
- Set the starting number and digit count.
- Reuse the smallest missing number before creating the next larger number.
- Create and open the new Markdown file from the command palette.
Usage
- Open Obsidian Settings.
- Go to Community plugins and enable Auto Sequential Filename.
- Open the plugin settings.
- Add a target folder configuration.
- Run the command
创建顺序文件from the command palette. - Select the target folder.
Example configuration:
| Folder | Prefix | Start number | Digits | Result |
|---|---|---|---|---|
15_关系/公司列表 | GS | 1 | 4 | GS0001.md |
15_关系/人员列表 | RY | 1 | 4 | RY0001.md |
If GS0001.md and GS0003.md already exist, the plugin creates GS0002.md first.
Manual installation
- Download
main.jsandmanifest.jsonfrom the latest GitHub release. - Create this folder in your vault:
.obsidian/plugins/auto-seq-filename/. - Put both files in that folder.
- Reload Obsidian and enable the plugin.
Development
npm install
npm run build
Release
- Make sure
manifest.jsonandpackage.jsonuse the same version. - Run
npm run build. - Create a GitHub release whose tag matches the manifest version, for example
1.0.0. - Upload the release assets listed below.
- Submit the GitHub repository URL in the Obsidian community plugin directory.
Release assets should include:
main.jsmanifest.jsonstyles.css
Community plugin submission checklist
README.mdexplains what the plugin does and how to use it.LICENSEis present.manifest.jsonhas a stable plugin id, name, version, and description.data.jsonis not published because it contains local user settings.- GitHub release tag matches
manifest.jsonversion, for example1.0.0.
License
MIT
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.