A personal knowledge management and sharing system for VSCode

Overview

Foam

๐Ÿ‘€ This is an early stage project under rapid development. For updates join the Foam community Discord! ๐Ÿ’ฌ

All Contributors

Discord Chat

Foam is a personal knowledge management and sharing system inspired by Roam Research, built on Visual Studio Code and GitHub.

You can use Foam for organising your research, keeping re-discoverable notes, writing long-form content and, optionally, publishing it to the web.

Foam is free, open source, and extremely extensible to suit your personal workflow. You own the information you create with Foam, and you're free to share it, and collaborate on it with anyone you want.

How do I use Foam?

Whether you want to build a Second Brain or a Zettelkasten, write a book, or just get better at long-term learning, Foam can help you organise your thoughts if you follow these simple rules:

  1. Create a single Foam workspace for all your knowledge and research following the [Getting started] guide.
  2. Write your thoughts in markdown documents (I like to call them Bubbles, but that might be more than a little twee). These documents should be atomic: Put things that belong together into a single document, and limit its content to that single topic. (source)
  3. Use Foam's shortcuts and autocompletions to link your thoughts together with [[wiki-links]], and navigate between them to explore your knowledge graph.
  4. Get an overview of your Foam workspace using the [Graph Visualisation], and discover relationships between your thoughts with the use of [Backlinking].

Foam kitchen sink, showing a few of the key features

Foam is a like a bathtub: What you get out of it depends on what you put into it.

Learn more

Head over to the ๐Ÿ‘‰ Published version of this Foam workspace to see Foam in action and read the rest of the documentation!

Quick links to next documentation sections

You can also browse the docs folder.

License

Foam is licensed under the MIT license.

Contributors โœจ

Thanks goes to these wonderful people (emoji key):


Jani Evรคkallio

๐Ÿ’ป ๐Ÿ“–

Joe Previte

๐Ÿ’ป ๐Ÿ“–

Riccardo

๐Ÿ’ป ๐Ÿ“–

Janne Ojanaho

๐Ÿ’ป ๐Ÿ“–

Paul Shen

๐Ÿ“–

coffenbacher

๐Ÿ“–

Mathieu Dutour

๐Ÿ“–

Michael Hansen

๐Ÿ“–

David Nadlinger

๐Ÿ“–

Fernando

๐Ÿ“–

Juan Gonzalez

๐Ÿ“–

Louie Christie

๐Ÿ“–

Sandro

๐Ÿ“–

Simon Knott

๐Ÿ“–

Steven

๐Ÿ“–

Tim

๐Ÿ“–

Saurav Khdoolia

๐Ÿ“–

Ankit Tiwari

๐Ÿ“– โš ๏ธ ๐Ÿ’ป

Ayush Baweja

๐Ÿ“–

TaiChi-IO

๐Ÿ“–

Juan F Gonzalez

๐Ÿ“–

Sanket Dasgupta

๐Ÿ“– ๐Ÿ’ป

Nicholas Stafie

๐Ÿ“–

Francis Hamel

๐Ÿ’ป

digiguru

๐Ÿ’ป ๐Ÿ“–

CHIRAG SINGHAL

๐Ÿ’ป

Jonathan Carter

๐Ÿ“–

Julian Elve

๐Ÿ“–

Thomas Koppelaar

๐Ÿ’ฌ ๐Ÿ’ป ๐Ÿ““

Akshay

๐Ÿ’ป

John Lindquist

๐Ÿ“–

Ashwin Ramaswami

๐Ÿ“–

Claudio Canales

๐Ÿ“–

vitaly-pevgonen

๐Ÿ“–

Dmitry Shemetov

๐Ÿ“–

hooncp

๐Ÿ“–

Martin Laws

๐Ÿ“–

Sean K Smith

๐Ÿ’ป

Kevin Neely

๐Ÿ“–

Arief Rahmansyah

๐Ÿ“–

Vishesh Handa

๐Ÿ“–

Hitesh Kumar

??

Spencer Woo

๐Ÿ“–

ingalless

๐Ÿ’ป ๐Ÿ“–

Josรฉ Duarte

๐Ÿ’ป ๐Ÿ“–

Yenly

๐Ÿ“–

hikerpig

๐Ÿ’ป

Sigfried Gold

๐Ÿ“–

Tristan Sokol

๐Ÿ’ป

Danil Rodin

๐Ÿ“–

Scott Williams

๐Ÿ“–

jackiexiao

๐Ÿ“–

John B Nelson

๐Ÿ“–

Asif Mehedi

๐Ÿ“–

Tan Li

๐Ÿ’ป

Shauna Gordon

๐Ÿ“–

Mike Cluck

๐Ÿ’ป

Brandon Pugh

๐Ÿ’ป

Max Davitt

๐Ÿ“–

Brian Anglin

๐Ÿ“–

elswork

๐Ÿ“–

lรฉon h

๐Ÿ’ป

Nikhil Nygaard

๐Ÿ“–

Mark Dixon

๐Ÿ’ป

Joel James

๐Ÿ’ป

Hashiguchi Ryo

๐Ÿ“–

Michael Overmeyer

๐Ÿ’ป

This project follows the all-contributors specification. Contributions of any kind welcome!

Issues
  • Issue #530: Graph Improvements

    Issue #530: Graph Improvements

    Hello! This is my first attempt at contributing to an open source project. I attempted to address many of the areas identified in regards to the graph visualization. I'm happy with the outcome, but I did make a lot of changes to the core graph logic. It's all backwards compatible as far as I can tell, aside from the actual visualization. It could be made to work with the old force-graph, but I chose to implement cytoscape.js both for handling the graph data in core and the visualization in the webview. I don't know how fast this is. I don't know how to test for that. The highlights:

    • ~~reworked foam-core/graph by implementing cytoscape.js to handle all of the graph data~~
    • implemented a basic gui and filtering in the data visualization (dat.gui made filtering kind of weird, should a panel be used instead?)
    • ~~implemented a command to expose the graph json (I'm fairly certain I put this in the wrong place)~~
    • add color: "red" to yaml frontmatter to change node colors easily. Accepts these formats: "red" / "#ff0000" / rgb(255,0,0)
    • highlight nodes based on text search (todo: use regex instead of simple string matching)
    • folder hierarchy view
    • visualize tags on graph
    • filter by tagged nodes (todo: implement filtering by specific tags)
    • limit graph view to selected nodes (Hold shift or ctrl to add nodes to selection, or use box select. Note: this doesn't play well with any of the other filters. I need update the gui to disable the other parameters when this is selected.)

    I'm still working on the styling, but it is still customizable. The formatting is different though so try something like this to test it out:

    "foam.graph.style" : { "styles": [{
          "selector": "node[type = 'note']",
          "style": {
            "background-color": "cyan",
          }
        }, {
          "selector": "node[type = 'tag']",
          "style": {
            "background-color": "purple",
          }
        }, {
          "selector": "node[type = 'placeholder']",
          "style": {
            "background-color": "pink",
          }
        }
      ]}
    

    Hopefully this works out and can be used as a basis for further improvements. I'm very new to typescript and vscode extensions, so I'm sure there is room for improvement. Let me know and I'll try to get things fixed as soon as I can.

    opened by dannysemi 34
  • [

    ["BUG"] Foam Graph uses inappropriate amount of CPU

    Describe the bug

    As soon as I open the Foam Graph two electron processes starts hogging a questionable high amount of CPU performance. On a workspace with around a dozen notes(i.e. nodes in the graph) they are both between 10% and 15% while on a workspace with ~330 notes one is at roughly 65-75% and the other at a quite stable ~24-26%. Numbers according to htop and on an AMD Ryzen 5 3600

    This is without any interaction with the graph and even if VS Code is on a workspace that isn't even being displayed

    To Reproduce

    1. Check a process manager like htop for the current list of processes requiring the most CPU performance
    2. Open VS Code with your Foam Workspace (which should not yet show a CPU load spike)
    3. Open the Foam Graph and probably observe two new processes hogging roughly an entire CPU core between them

    Expected behavior

    Not hog an absurdly high amount of CPU performance. The Markdown Links graph requires a similar amount of CPU when opening it and occasionally during panning, but this returns to baseline shortly after again.

    Additional Notes

    I assume this is something with the interactivity and live update feature. Potentially this could be deactivated via an option until the exact cause of this issue is found.

    bug foam-dataviz 
    opened by fmagin 31
  • Automate adding contributors via GitHub Action

    Automate adding contributors via GitHub Action

    It would be great if we had a GitHub Action which ran on "merge pull request" and then opened a new pull request to add a person to the all-contributors table in the README. It wouldn't solve all the use cases for adding contributors to the table, but a majority of them.

    Happy to help guide/mentor someone if they want to pick this up.

    help wanted good first issue 
    opened by jsjoeio 28
  • Remove legacy github slugger

    Remove legacy github slugger

    @riccardoferretti I'm not sure how do you regenerate yarn.lock so I've only changed package.json.

    I decided to leave the slug term as it's used in many places, I think it has a legitimate meaning. Regarding the references used to find resources in the workspace, one could say a reference is:

    • An URI
    • Or a slug (string) which can be:
      • Absolute
      • Relative
      • An identifier

    AFAICS the current code is consistent with this terminology.

    I've added a refactor label since I expect to send a few more purely-refactoring PRs, but feel free to delete or rename it.

    refactor 
    opened by memeplex 26
  • WIP: Move selected text into a new note and auto create a backlink

    WIP: Move selected text into a new note and auto create a backlink

    This pr resolves #653 , the suggestion adds the functionality to create a new note for a piece of selected text. It will use the functionalities as introduced by @movermeyer to create a new note from the default template or select a template. I've added a configuration to configure foam to always select a note template if desired. Setting it false means it will use the default template.

    To keep behaviour similar to the other two new note command I am reusing that code as much as possible. It simply adds some additional text and view behaviour to the existing methods. This should keep the user interaction consistent and will reduce maintenance work. I need to add tests and do some more manual testing, but first want to validate the approach with @movermeyer and @riccardoferretti. You are welcome to leave your suggestions and comments.

    note-selection

    opened by pderaaij 25
  • Error linking file in subdirectory

    Error linking file in subdirectory

    • Foam version: v0.15.2
    • Platform: macOS Big Sur
    • Issue occur on the foam template repo: Yes

    Summary

    Steps to reproduce

    1. Create a directory d with files a.md and b.md
    2. Add [[d/b]] to a.md
    3. Follow that link: it will offer to create b and the fail because b already exists.

    https://user-images.githubusercontent.com/2845433/139410901-3630da90-297c-4d15-8e14-09901a1c4add.mov

    bug 
    opened by memeplex 24
  • fix: fixing casing issue for windows

    fix: fixing casing issue for windows

    Fixes #488

    On Windows, the uri util file contains a compare relative paths with posix functions. The drive letters might not match on Windows (unique problem on win32 platform).

    This fix introduces a small utility that is only relevant to Windows platform that would normalize drive letters in paths.

    opened by kenotron 23
  • Slugification of wikilinks (was: Foam Graph showing two entries for same wikilink reference)

    Slugification of wikilinks (was: Foam Graph showing two entries for same wikilink reference)

    • Foam version: v0.10.0
    • Platform: Mac (Big Sur 11.2.1)
    • Issue occur on the foam template repo: Yes

    Summary Foam Graph shows two entries for same note. One entry is shown orphan which is active. The actual link is shown as inactive.

    Steps to reproduce

    1. I created a daily journal entry, and types a wiki link to create it
    2. Click on the wiki link to create the desired page
    3. As the page got created in same journal folder I moved it to root folder

    Additional information I have attached a demo project with only the actions I have taken and the foam graph has that issue The project started from Foam Template and I have added some extension suggestions which I am already using

    foam-graph-issue

    foam-graph-test.zip

    discussion 
    opened by tusharjoshi 23
  • [

    ["BUG"] "Show Graph" command produced a black background without nodes

    To Reproduce Reload VSCode and use Foam: Show Graph command.

    Screenshots There are some files in my repository but foam did't show these nodes. image

    Supplement Sometimes after linking a file to another, and reuse the command, both the two files' nodes will appear. Or type any words in a file, and reuse the command, the file's node will also appear. But if you reload VSCode and reuse the command, all the nodes will disappear again. It's not stable and I'm not sure when and why this bug will appear, as if it will only show the nodes which has been modifed. Once VSCode is reloaded, all the files will be regarded as "not modified". By the way, all the links in my repository are regular markdown links, not wikilinks.

    This is the contrast between Foam: Show Graph command (left) and Markdown Links: Show Graph command (right) : image

    Test Environment Windows 10 version 1909 Plugin version 0.7.0

    bug 
    opened by ysl2 21
  • Improve documentation of vscode extension

    Improve documentation of vscode extension

    • [ ] improve extension manifest (see https://code.visualstudio.com/api/references/extension-manifest#marketplace-presentation-tips)
    • [x] update the docs/ directory to separate ideas/features/thoughts/...
    • [x] update README to become entry point into structured documentation for existing features
    • [ ] test the presentation of the newly released extension in the marketplace (e.g. title, icon, readme, links to repo/bugs/..)
    documentation help wanted 
    opened by riccardoferretti 21
  • Path bug in Windows

    Path bug in Windows

    • Foam version: v0.9.1
    • Platform: Windows
    • Issue occur on the foam template repo: Not sure

    Summary

    Windows wiki-link bug

    The Windows path is very weird. It's not at all portable because it is not a relative path.

    Steps to reproduce

    1. Add a link to todo.md by [[todo]]
    2. Ctrl + S

    Additional information

    Feel free to attach any of the following that might help with debugging the issue:

    • screenshots
    • a zip with a minimal repo to reproduce the issue
    • the Foam log in VsCode (see instructions)
    bug 
    opened by just1a-person 19
  • Allow

    Allow "daily note" file template to have `ww`, to allow for weekly notes

    Is your feature request related to a problem? Please describe.

    It isn't possible to have a weekly journal note instead of a daily one.

    Describe the solution you'd like

    Right now daily notes can have their filename customized like so:

      "foam.openDailyNote.filenameFormat": "'daily-note'-yyyy-mm-dd",
    

    This can be edited to, say, have a monthly note:

      "foam.openDailyNote.filenameFormat": "'daily-note'-yyyy-mm",
    

    I would love to add the ww template value in there so I can have a weekly note:

      "foam.openDailyNote.filenameFormat": "'daily-note'-yyyy-ww",
    

    This would be filled in by the week # of the year.

    Describe alternatives you've considered

    Making a whole new feature for weekly notes with a different command. That could be necessary if you want BOTH weekly & daily notes. I, however, don't.

    Implementing the way above doesnt block making a weekly feature later.

    Screenshots or Videos

    No response

    opened by dmurph 4
  • FeatReq: Autocomplete links with notes titles, not filenames

    FeatReq: Autocomplete links with notes titles, not filenames

    Is your feature request related to a problem? Please describe.

    When autocompleting link opened with [[: Current behavior: Foam shows proposition list, where you can find filenames of available documents with additional preview of the content. When position is picked, Foam fills [[]] link with shortest possible file identifier like [[file1]] for file1.md.

    Expected behavior: Foam shows proposition list, where you can find titles of available documents, with additional preview that may (not must) have a path to the document. When position is picked, Foam fills [[]] link with file identifier aliased with file title like [[file1|The title found in the file]] for file1.md.

    Motivation: When trying to use Foam to build so called Second Brain using Zettelkasten method I can see this problem. The metod says that each file/note should have unique identifier/filename that should be not mutable after note creation. The easiest approach to achieve this is to use for example timestamp as a filename. But this brings us to the problem described above, when you have several files named like:

    20210511022607.md
    20210512085325.md
    20210515161743.md
    20210511124221.md
    20210521150143.md
    

    and you try to create a link to another note, the only thing you see is this list of numbers. When you want to find particular note you have to check previews. It would be very helpful instead of seeing this list of filenames, to see list of note titles extracted by for example regex ^# .*$ and presented like this:

    Title1 - 20210511022607.md
    Some long title - 20210512085325.md
    Other title - 20210515161743.md
    Another title - 20210511124221.md
    Title over 9000 - 20210521150143.md
    

    Filenames may or may not be presented on the list (it may be a part of preview), but most important, the title of the note should be searchable. And after picking the note Foam should fill the link with the filename aliased with the title like this: [[20210512085325|Some long title]].

    This new approach also should link with some refactoring. When changing title of the note, all references (aliases in links) should also change (option for that). In this approach the note filename is constant so we don't have to be concerned about filename, link change.

    Update: Also, there there should be a setting that enforce new file filename to particular format, so no matter which way the file is created (daily note, placeholder click) the filename should always be the same.

    Describe the solution you'd like

    Mostly described in the main description.

    How would I do this? Add three settings: Link autocompletion method <drop-box>: (filename|note title) Note title regex <string>: default(^# .*$) Change alias on note title change <bool> New file name format <string>: - something like Daily Note file format (update)

    And fill autocompletion box with appropriate content.

    Describe alternatives you've considered

    The idea is coming from Zettelkaster method:

    1. I have checked how Obsidian is doing it. Obsidian has a json database, when it connects physical filename, note title and generated uuid as one entity, and fills links with note title. Having this DB application knows how to react to the changes. I think this is one of the best solutions to this problem, but it may be an overkill for what I would want to achieve.
    2. the main problem on achieving this is to somehow ensure filenames uniqueness also keeping the autocomplete list readable. It can be also done by naming the file as a sum of NoteTitle and timestamp like Another_title-20210511124221.md. In the list one can see some descriptive text, but link created from this is simply [[Another_title-20210511124221.md]] that have to be manually changed to [[Another_title-20210511124221.md|Another title]], and also there is no synchronization when the note changes title. In that case one must rename the file, and manually follow all references to change the alias (or most probably use sed for this).

    Screenshots or Videos

    No response

    enhancement help wanted good first issue foam-vscode 
    opened by XobSod 6
  • Allow users to select the foam template as creating a new note by clicking on the link in the preview popup

    Allow users to select the foam template as creating a new note by clicking on the link in the preview popup

    Is your feature request related to a problem? Please describe.

    Steps to produce:

    1. Open a foam project which contains foam templates, then open a markdown file.
    2. Add a new wiki link, ex. [[wiki-link| Wiki Link]], the associated markdown file was not created.
    3. Hover on the wiki link.
    4. Wait to see the preview popup, then click on Create note for 'wiki-link'.
    5. The file was created without asking user to select the foam template.

    Describe the solution you'd like

    As a user, I expect I can select the foam template after clicking on the link, similar to the feature Create new note from template.

    Describe alternatives you've considered

    I have some suggestions: 1 Change behaviour on clicking on the preview popup link. 2. Keep it, but add a new link to allow create a new note from the foam template. 3. Add a setting to allow users to choose the behaviour they want.

    Screenshots or Videos

    No response

    help wanted good first issue foam-template 
    opened by ansidev 2
  • `cmd + click` Create a file in the same level directory instead of the root directory.

    `cmd + click` Create a file in the same level directory instead of the root directory.

    Is your feature request related to a problem? Please describe.

    cmd + click Create a file in the same level directory instead of the root directory

    Describe the solution you'd like

    cmd + click Create a file in the same level directory instead of the root directory

    Describe alternatives you've considered

    A path config like "${currentFolder}"

    Screenshots or Videos

    image image
    opened by faydanube 6
  • Workspace-specific Foam functionality

    Workspace-specific Foam functionality

    Is your feature request related to a problem? Please describe.

    First, thank you all so much for the amazing package. I'm just starting to play around with it, but there is a lot of potential here. And the vscode integration is just great.

    This is related to #683. A lot was discussed in that pull request, but it looks like it stalled, so I just wanted to bump it, as some of the functionalities discussed would be extremely useful. Specifically, it looks like the contributors were a bit overwhelmed by all the possible options that might need to be implemented for both primary and edge cases. So, I'm just providing my use case to highlight some core functionality that might be valuable to the majority of folks, and encouraging the contributors to worry about edge cases later (perhaps the suggestion is naive, but sometimes perfect can be the enemy of good enough -- and I mean that with the best of intentions, as I think this project is already great).

    Describe the solution you'd like

    My use case is that I have a "main" second brain for personal use, so the core functionalities already provided work great. But I also have "satellite" second brains for specific projects with collaborators. For my satellite projects I would like to be able to store all my Foam notes in a subdirectory to the main project, as there are other concerns that need to be placed in the main directory of my workspace (e.g., website functionalities). I also don't want Foam to think all my other folders need to be mapped/connected (e.g., via the graph), but don't want to have to add every single folder to the exceptions in the settings.json file (which I think I would need to do if using Foam from the project root).

    In that context, it would useful to just be able to change the location of the ${projectRoot} to something else. I only every plan to use Foam in the context of a workspace, if that helps simplify things (I think that's probably most other users, as well).

    Describe alternatives you've considered

    For my satellite projects, I'm hosting Foam notes in a notes/ subdirectory. When I create new linked notes using [[]] they are automatically generated in this directory, which is nice, but if I create new notes from the command palette, they are created in the workspace's root, so I have to manually move them, which is not terrible, but does become a hassle on particularly prolific note taking days.

    Screenshots or Videos

    No response

    opened by wetlandscapes 1
Releases(v0.19.3)
  • v0.19.3(Aug 4, 2022)

  • v0.19.2(Aug 4, 2022)

    Fixes and Improvements:

    • Added support for angle markdown links (#1044)
    • Filter out invalid file name chars when creating note (#1042)

    Internal:

    • Reorganized docs (#1031, thanks @infogulch)
    • Fixed documentation links (#1046)
    • Preview code refactoring
    Source code(tar.gz)
    Source code(zip)
  • v0.19.1(Jul 12, 2022)

  • v0.19.0(Jul 7, 2022)

    New Features:

    • Support for attachments (PDF) and images (#1027)
    • Support for opening day notes for other days as well (#1026, thanks @alper)
    Source code(tar.gz)
    Source code(zip)
  • v0.18.5(Jun 29, 2022)

    Fixes and Improvements:

    • Support for alias YAML property to define note alias (#1014 - thanks @lingyv-li)

    Internal:

    • Improved extension bundling (#1015 - thanks @lingyv-li)
    • Use vscode.workspace.fs instead of fs (#1005 - thanks @joshdover)
    Source code(tar.gz)
    Source code(zip)
  • v0.18.4(Jun 3, 2022)

    Fixes and Improvements:

    • move past ]] when writing wikilinks (#998 - thanks @Lauviah0622)
    • highlight improvements (#890 - thanks @memeplex)
    Source code(tar.gz)
    Source code(zip)
  • v0.18.2(Apr 14, 2022)

    Fixes and Improvements:

    • Fixed parsing error on empty direct links (#980 - thanks @chrisUsick)
    • Improved rendering in preview of wikilinks that have link definitions (#979 - thanks @josephdecock)
    • Restored handling of section-only wikilinks (#981)
    Source code(tar.gz)
    Source code(zip)
  • v0.18.1(Apr 13, 2022)

    Fixes and Improvements:

    • Fixed parsing error for direct links with square brackets in them (#977)
    • Improved markdown direct link resolution (#972)
    • Improved templates support for custom paths (#970)
    Source code(tar.gz)
    Source code(zip)
  • v0.18.0(Apr 11, 2022)

  • v0.17.8(Apr 1, 2022)

    Fixes and Improvements:

    • Do not add ignored files to Foam upon change (#480)
    • Restore full use of editor.action.openLink (#693)
    • Minor performance improvements
    Source code(tar.gz)
    Source code(zip)
  • v0.17.7(Mar 29, 2022)

  • v0.17.6(Mar 3, 2022)

  • v0.17.5(Feb 22, 2022)

  • v0.17.4(Feb 13, 2022)

    Fixes and Improvements:

    • Improvements to Foam variables in templates (#882 - thanks @movermeyer)
      • Foam variables can now be used just any other VS Code variables, including in combination with placeholders and transformers
    Source code(tar.gz)
    Source code(zip)
  • v0.17.3(Jan 14, 2022)

    Fixes and Improvements:

    • Fixed autocompletion with tags (#885 - thanks @memeplex)
    • Improved "Open Daily Note" to be usabled in tasks (#897 - thanks @MCluck90)
    Source code(tar.gz)
    Source code(zip)
  • v0.17.2(Jan 14, 2022)

    Fixes and Improvements:

    • Improved support for wikilinks in titles (#878)
    • Use syntax injection for wikilinks (#876 - thanks @memeplex)
    • Fix when applying text edits in last line

    Internal:

    • DX: Clean up of testing setup (#881 - thanks @memeplex)
    Source code(tar.gz)
    Source code(zip)
  • v0.17.1(Dec 16, 2021)

    Fixes and Improvements:

    • Decorate markdown files only (#857)
    • Fix template placeholders issue (#859)
    • Improved replacement range for link completion

    Internal:

    • Major URI/path handling refactoring (#858 - thanks @memeplex)
    Source code(tar.gz)
    Source code(zip)
  • v0.17.0(Dec 8, 2021)

    Features:

    • Added first class support for sections (#856)
      • Sections can be referred to in wikilinks
      • Sections can be embedded
      • Autocompletion for sections
      • Diagnostic for sections
      • Embed sections
    Source code(tar.gz)
    Source code(zip)
  • v0.16.1(Dec 1, 2021)

  • v0.16.0(Nov 24, 2021)

    Features:

    • Added support for unique wikilink identifiers (#841)
      • This change allows files that have the same name to be uniquely referenced as wikilinks
      • BREAKING CHANGE: wikilinks to attachments must now include the extension
    • Added diagnostics for ambiguous wikilinks, with quick fixes available (#844)
    • Added support for unique wikilinks in autocompletion (#845)
    Source code(tar.gz)
    Source code(zip)
  • v0.15.9(Nov 23, 2021)

  • v0.15.8(Nov 21, 2021)

  • v0.15.7(Nov 21, 2021)

  • v0.15.6(Nov 21, 2021)

  • v0.15.5(Nov 15, 2021)

    Fixes and Improvements:

    • Major improvement in navigation. Use link definitions and link references (#821 - thanks @JonasSprenger )
    • Fixed bug showing in hover reference the same more than once when it had multiple links to another (#822)

    Internal:

    • Foam URI refactoring (#820)
    • Template service refactoring (#825)
    Source code(tar.gz)
    Source code(zip)
  • v0.15.4(Nov 8, 2021)

    Fixes and Improvements:

    • Detached Foam URI from VS Code URI. This should improve several path related issues in Windows. Given how core this change is, the release is just about this refactoring to easily detect possible side effects.
    Source code(tar.gz)
    Source code(zip)
  • v0.15.3(Nov 8, 2021)

    Fixes and Improvements:

    • Avoid delaying decorations on editor switch (#811 - thanks @memeplex)
    • Fix preview issue when embedding a note and using reference definitions (#808 - thanks @pderaaij)
    Source code(tar.gz)
    Source code(zip)
  • v0.15.2(Oct 27, 2021)

    Features:

    • Added FOAM_DATE_* template variables (#781)

    Fixes and Improvements:

    • Dataviz: apply note type color to filter item label
    • Dataviz: optimized rendering of graph to reduce load on CPU (#795)
    • Preview: improved tag highlight in preview (#785 - thanks @pderaaij)
    • Better handling of link reference definition (#786 - thanks @pderaaij)
    • Link decorations are now enabled by default (can be turned off in settings)
    Source code(tar.gz)
    Source code(zip)
  • v0.15.0(Oct 4, 2021)

    Features:

    • Preview on hover for wikilinks (#728 - thanks @JonasSprenger)
    • Added tags and controls to graph dataviz (#737 - thanks @dannysemi)

    Fixes and Improvements:

    • Improved tags parsing (#733)
    • Fixed support for resources named like JS Object methods (#729 - thanks @JonasSprenger)
    Source code(tar.gz)
    Source code(zip)
  • v0.14.2(Jul 24, 2021)

    Features:

    • Autocompletion for tags (#708 - thanks @pderaaij)
    • Use templates for new note created from wikilink (#712 - thanks @movermeyer)

    Fixes and Improvements:

    • Improved performance of initial file loading (#730 - thanks @pderaaij)
    Source code(tar.gz)
    Source code(zip)
Owner
Foam
Developing tools for thought
Foam
Modern ls command with vscode like File Icon and Git Integrations. Written in Golang

logo-ls modern ls command with beautiful Icons and Git Integrations . Written in Golang Command and Arguments supported are listed in HELP.md Table of

Yash Handa 907 Aug 11, 2022
Libraries and CLIs for my personal all-in-one productivity system including components like bookmarks, notes, todos, projects, etc.

bntp.go Libraries and CLIs for my personal all-in-one productivity system including components like bookmarks, notes, todos, projects, etc. Neovim int

Jonas Mรผhlmann 11 Apr 29, 2022
CLI for Shamir's Secret Sharing and AES key generation, encryption, and decryption.

Shush ?? This simple program will help you run Shamir's Secret Sharing algorithm on any file using the split and merge commands.

null 24 Feb 1, 2022
Creating a simple CLI tool in the Go Programming Language for personal learning and fun

Creating a simple CLI tool in the Go Programming Language for personal learning and fun Open to feedback :) Build docker dev environment docker build

Mohamed Abukar 4 Dec 12, 2021
StudentMgmtSystem - Project for Student Management System and use of CURD Operation

StudentMgmtSystem Project for Student Management System and use of CURD Operatio

null 0 Jan 4, 2022
The personal information dashboard for your terminal

WTF (aka 'wtfutil') is the personal information dashboard for your terminal, providing at-a-glance access to your very important but infrequently-need

WTFUtil 13.7k Aug 12, 2022
Upterm is an open-source solution for sharing terminal sessions instantly over the public internet via secure tunnels.

Upterm is an open-source solution for sharing terminal sessions instantly over the public internet via secure tunnels.

Owen Ou 503 Aug 8, 2022
Grit is an experimental personal task manager that represents tasks as nodes of a multitree

Grit is an experimental personal task manager that represents tasks as nodes of a multitree, a class of directed acyclic graphs. The structure en

Tomasz Klimczak 1.6k Aug 12, 2022
A personal collection of handy CLI tools

Toolkit A personal collection of handy CLI tools Installation 1.) Download and extract the ZIP package for the the latest release 2.) Copy the appropr

Luke Johnson 0 Nov 8, 2021
Clipsync: a high performance clipboard sharing application for linux

clipsync: Clipboard sync Clipsync is a high performance clipboard sharing applic

Zachary Huff 2 Jun 22, 2022
remindme is a simple application to set reminders from the CLI that integrates with your system's notification system.

remindme remindme is a simple application to set reminders from the CLI that integrates with your system's notification system. Examples Once the serv

Brian Downs 29 Jan 1, 2022
Jsos - A operating system that runs system-level javascript, based on the Linux kernel

JsOS ?? An linux-based operating system that runs Javascript code at the system-

Theo Paris 1 Mar 8, 2022
A Target Tracking , NoteTaking , CheckLists and Data Management GUI App for Bug Hunter's and Pentesters.

Screenshots Features โ€ข Installation โ€ข Usage โ€ข Features โ€ข Notes โ€ข Sandman A Target Tracking , NoteTaking , CheckLists and Data Management GUI App for B

Tarun Koyalwar 23 Aug 8, 2022
tfacon is a CLI tool for connecting Test Management Platforms and Test Failure Analysis Classifier.

Test Failure Classifier Connector Description tfacon is a CLI tool for connecting Test Management Platforms and Test Failure Analysis Classifier. Test

Red Hat Quality Engineering 3 Jun 23, 2022
Go library and CLI utility for /etc/hosts management.

Etc Hosts Management Utility & Go Library /etc/hosts Management It is easy to open your /etc/hosts file in text editor and add or remove entries. Howe

txn2: Kubernetes apps and system utilities. 270 Jul 26, 2022
wrench - Schema management tool for Cloud Spanner -

wrench wrench is a schema management tool for Cloud Spanner. Please feel free to report issues and send pull requests, but note that this application

Cloud Spanner Ecosystem 164 Aug 2, 2022
SSH Lightweight management tools

tssh golang ๅฎž็Žฐ็š„ssh ๅทฅๅ…ท ๅฎ‰่ฃ… ไธ‹่ฝฝๅฎ‰่ฃ… ไธ‹่ฝฝๅœฐๅ€ release windows็”จๆˆท่ฏทๆ‰‹ๅŠจไธ‹่ฝฝ๏ผŒๆš‚ๆ—ถไธๆไพ›ไธ€้”ฎๅฎ‰่ฃ…ๆจกๅผ๏ผˆ ไธป่ฆๆ˜ฏๆ‰นๅค„็†่„šๆœฌไธไผšๅ†™ ๏ผ‰ Macไธ€้”ฎๅฎ‰่ฃ… /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.

lrs 123 Aug 8, 2022
a work time management CLI tool for any platform

english |ๆ—ฅๆœฌ่ชž jobgosh | job management tool made with golang for shell a multi-platform work time management CLI tool to track and improve your day to

ๅฅฅ็”ฐใ€€้พ้ฆฌ 10 May 16, 2022
Google KMS backed Solana key management CLI tool

solana-kms solana-kms is a Google KMS backed Solana token management CLI utility. The main purpose of the tool is to ensure that the private key is ne

kubetrail.io 2 Jan 13, 2022