viddo / atom-textual-velocity Goto Github PK

Steps to Reproduce:

1. Search for test vår älg öl
2. Press enter> to create new file
3. Copy search term and add it as file content -- save file
4. Search for "test vår älg öl" again

Expected behavior:

Should see the matched file, with the matching word highlighted in the filename

Actual behavior:

One sees the matched file, but only because it has a match in the file content. The title is still (incorrectly) w/o unhighlighted.

Investigation:

The root issue is a mismatch between keyboard and the filenames and how unicode characters are stored. on MacOSX they are stored in decomposed form, e.g. ä is really two distinct characters a¨, even though they are presented together when rendered.

Considering it's out of scope to change the underlying filesystem, and out-of-scope of the underlying search library (who should not need to consider filenames), the most reasonable solution I can think of is to modify the parsed-path field to remap the filename into characters that will match keyboard input, i.e. unicode composed form from the outset.

Related sources:

• http://stackoverflow.com/questions/28581054/unicode-composed-and-decomposed-forms
• https://developer.apple.com/library/content/qa/qa1173/_index.html
• https://en.wikipedia.org/wiki/Unicode_equivalence

Possibly other non-umlauts characters are also affected -- if you run into this case please do report them here.

Workaround (until this issue is fixed):

Add the filename umlaut'ed words in the file content, that way it will match there at least and thus appear in the search result.

First of all, thank you so much for your work! Textual Velocity is amazing and it's exactly what I've been looking for since several months. Thank you!

To optimize the search, I would suggest to make tile-matches a priority, i.e. when the search terms are part of the filetitle, make this file come first even if there are more matches in the note body of other notes.

At the moment only the first token* is used to highlighted in the match of the title and content. Need to consider implications of adding more though.

*Token = "this and that" would have the tokens ["this", "and", "that"]

I cannot type capital letters in the search field. For search of course, this is of minor importance, but when it comes to creating files from the keywords + Enter, capital letters can be helpful.

OS: Windows 10

In my note base I use the navigate package which allows me to jump to a note when its filename is part of the text-body of another note, e.g. I mark [[link]] and press a shortcut, so that link.txt is opened immediately.

This only works when the link.txt is in the same directory. So I keep all my notes in one directory, also my #tag.txt notes, which contain lists of all notes that contain a certain #tag.

I do not want these notes to be displayed at the top of the search results. Is there an option to exclude notes with a certain filename from search? (Before textual velocity I used docfetcher, which allowed me to exclude all notes stasrting with # from indexing)

Need to considering how the columns should be resized on window resize etc.

Steps to reproduce

1. Open first three notes (i.e. select, focus on editor to open text editor)
2. Click on the first note (should now be selected)
3. ↓ three times "quickly" -- but not too quickly, ~10-50ms

Expected behavior:

Should preview the 3rd note

Actual behavior:

Previewing the 2rd note

Investigation

It appears to be some kind of race condition related to selection and the https://github.com/viddo/atom-textual-velocity/blob/bb2ba0147866aaf05acac89a43b78c4d8f1d99e9/lib/epics/active-pane-item.js epic which observes the pane changes. For some reason it triggers an event for the 2nd pane item even though in theory it should be debounced when the 3rd item is selected.

It's happening on some window sizes, due to the width of the grid is based on percentage so the column width is slightly too small to fit the actual icon.

Quick solution: Change the default widths

Long-term solution: Resizable columns #3 - with sensible min-width defaults.

Right now when selecting a note it always opens a preview editor which stays in the background. More often than not I find the preview is "getting in the way". E.g. closing an open note text editor it re-selects the previous note upon the preview is opened next, even though I'm done with it. Therefore, I'm considering the following changes:

1. Upon an open-selected-note (enter/double-click the note) or focus-preview action:

   • Current behavior: A text editor is opened & focused (preview editor left open in the background).
   • Proposed change: Always close the preview (in addition to open&focus the normal text editor).

2. When a note is selected:

   • Current behavior: A preview is always opened/updated.
   • Proposed behavior: If there exists a normal text editor that corresponds to the note open that editor instead and close the preview (if there is any) - If not, open/update the preview.

Thoughts? Or any other proposals?

Probably should do some more thorough "preflight" checks before starting the session:

• Check for funky paths, e.g.~/../../Dropbox/Notes, in particular on Windows (from #71)
• Check if path exists, and if not try to create it (and validate that can r/w that path)
• Check dir size/depth, and blacklist certain dirs (e.g. ~/) that are considered too big

Apparently, autosave does not work. When I enter a new word in the search field and open a new note, the old one is not shown any longer and changes are not saved (although autosave is activated for other documents). I'm not asked whether to keep changes.

I suggest to add autosave and also an option to open new notes in a new tab instead of closing the current note when another one is opened through search.

The key bindings don't work under linux when the editor is focused. I had to add something like the following to the keymap file:

'atom-text-editor':
'ctrl-shift-C': 'textual-velocity:toggle-panel'
'ctrl-`': 'textual-velocity:focus-on-search'

i get this error when I start a textual velocity. maybe Atom automatically updated itself so the package does not work anymore.

[email protected] – Module version mismatch. Expected 47, got 46.
[email protected] – Module version mismatch. Expected 47, got 46.
[email protected] – Module version mismatch. Expected 47, got 46.
[email protected] – Module version mismatch. Expected 47, got 46.

https://code.google.com/p/openmeta/
i.e. xattrs from files. only on OSX.

I wondered where tags of this package would be coming from as this is not documented. Extracting hashtags would be trivial.

Version 1.1.3 of atom-babel6-transpiler was just published.

This version is covered by your current version range and after updating it in your project the build failed.

atom-babel6-transpiler is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

At the time of writing, is using version 1.0.6 of chokidar, because any newer version fails to install/build (apm rebuild), need to investigate what the real issue is.

edit:
Related issues:

• mapbox/node-pre-gyp#188
• fsevents/fsevents#93

Other packages went with using https://github.com/shama/gaze instead.

1. Select an item
2. Rename a note

Atom Version: 1.12.0-beta1
Electron Version: 1.3.6
System: Mac OS X 10.10.5
Thrown From: textual-velocity package, v0.10.0

Stack Trace

Uncaught TypeError: Cannot read property 'replace' of undefined

At /Volumes/tv/.atom/packages/textual-velocity/lib/preview-element.js:13

TypeError: Cannot read property 'replace' of undefined
    at textual-velocity-preview.updatePreview (/Volumes/tv/.atom/packages/textual-velocity/lib/preview-element.js:13:26)
    at /Volumes/tv/.atom/packages/textual-velocity/lib/side-effects.js:184:21
    at /Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:980:16
    at /Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:395:23
    at Object.inTransaction (/Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:368:11)
    at Dispatcher.push (/Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:1146:24)
    at Dispatcher.handleEvent (/Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:1199:17)
    at /Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:232:17
    at /Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:1719:17
    at sender (/Volumes/tv/.atom/packages/textual-velocity/node_modules/baconjs/dist/Bacon.js:2139:14)

Expected result: No error thrown, preview to show the renamed file

Are you considering adding a note interlinking functionality? Or is this something that should be provided by another package? At this point I think a basic note interlink functionality would be useful, but allow it to be toggled to allow users to install other plugins for more advanced interlinking. (for example, my atom-plumber package which provides regex-based navigation)

For reference, here is how nvatom handled these links: https://github.com/seongjaelee/nvatom/blob/master/lib/interlink.coffee

Right-click on columns to see a menu with available columns, and be able to enable/disable columns to render

Hello!

Thank you so much for working on this package NV has been my favorite for years. Having this functionality through Atom is just beautiful.

I am aware velocity is WIP, so before bothering anyone with the details I was wondering if anyone else is having problems/inability to use default folder or custom folders, creating notes...? I would like to know if this is expected considering the stage of development or is it an issue. With the default path not even velocity panel shows up, with custom paths it shows up, but the notes end up in very strange places! E.g: ~/notes/~/Notes/note.md.

ATM, I have vanilla Atom 1.15.0 x64 on MacOS 10.11.6 (the only package installed is Atom-textual-velocity)
(removed all the packages, uninstalled Atom, cleaned the system before this just to make sure it is not my setup creating the problems)

Thanks for any feedback.

Apart from allowing for users to prioritize Title-matches in search, I would really appreciate an option to prioritize "Density" of the search results. So instead of showing the notes first with the most matches, show those first which have most matches per characters/word count...
For anyone who keeps longer articles (containing the same words that I use to search shorter notes) as part of his note directory, this would be great.

My personal notes are like 5Mb in total, it takes like 5 sec to load. Not horrible but could very likely be speeded up by some simple changes and profiling.

E.g. delay stat calls on each file to after all files are loaded.

Right now sorted by mdate in reverse chronological order. The sifter already supports sorting, so should not be too problematic to add.

Right now it's hardcoded to .md.

Although one can use a custom file extenson by simply appending it to the search string.

Hi,

for me, atom fails to install on Windows 10 (Visual Studio 2013, python 2.7 installed)
Could you please help me out?

C:\Users\User1.atom\packages>apm install textual-velocity
Installing textual-velocity to C:\Users\User1.atom\packages failed

[email protected] install C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\fs-xattr
node-gyp rebuild

C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\fs-xattr>if not defined npm_config_node_gyp (node "C:\Users\User1\AppData\Local\atom\app-1.8.0\resources\app\apm\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu erm�glichen, m�ssen Sie den Schalter "/m" hinzuf�gen.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(396,5): warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build. [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\fs-xattr\build\xattr.vcxproj]
error.cc
xattr.cc
..\src\xattr.cc(8): fatal error C1083: Datei (Include) kann nicht ge�ffnet werden: "sys/xattr.h": No such file or directory [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\fs-xattr\build\xattr.vcxproj]
..\src\error.cc(76): error C2065: 'ENOTBLK': nichtdeklarierter Bezeichner [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\fs-xattr\build\xattr.vcxproj]
..\src\error.cc(76): error C2051: case-Ausdruck ist keine Konstante [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\fs-xattr\build\xattr.vcxproj]

[email protected] install C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\sifter\node_modules\microtime
node-gyp rebuild

C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\sifter\node_modules\microtime>if not defined npm_config_node_gyp (node "C:\Users\User1\AppData\Local\atom\app-1.8.0\resources\app\apm\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu erm�glichen, m�ssen Sie den Schalter "/m" hinzuf�gen.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(396,5): warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build. [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\sifter\node_modules\microtime\build\microtime.vcxproj]
microtime.cc
Bibliothek "C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\sifter\node_modules\microtime\build\Release\microtime.lib" und Objekt "C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\sifter\node_modules\microtime\build\Release\microtime.exp" werden erstellt.
Code wird generiert.
Codegenerierung ist abgeschlossen.
microtime.vcxproj -> C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\sifter\node_modules\microtime\build\Release\microtime.node

[email protected] install C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils
node-gyp rebuild

C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils>if not defined npm_config_node_gyp (node "C:\Users\User1\AppData\Local\atom\app-1.8.0\resources\app\apm\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu erm�glichen, m�ssen Sie den Schalter "/m" hinzuf�gen.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(396,5): warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build. [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\libgit2.vcxproj]
annotated_commit.c
attr.c
attr_file.c
attrcache.c
blame.c
blame_git.c
blob.c
branch.c
buf_text.c
buffer.c
cache.c
checkout.c
cherrypick.c
clone.c
commit.c
commit_list.c
config.c
config_cache.c
crlf.c
config_file.c
curl_stream.c
date.c
delta-apply.c
delta.c
describe.c
diff.c
diff_driver.c
diff_file.c
diff_patch.c
diff_print.c
diff_stats.c
diff_tform.c
diff_xdiff.c
errors.c
fetch.c
fetchhead.c
filebuf.c
fileops.c
filter.c
fnmatch.c
global.c
graph.c
hash.c
hashsig.c
ident.c
ignore.c
index.c
indexer.c
iterator.c
merge.c
merge_file.c
message.c
mwindow.c
netops.c
notes.c
object.c
object_api.c
odb.c
odb_loose.c
odb_mempack.c
odb_pack.c
oid.c
oidarray.c
openssl_stream.c
pack-objects.c
pack.c
path.c
pathspec.c
pool.c
posix.c
pqueue.c
push.c
rebase.c
refdb.c
refdb_fs.c
reflog.c
refs.c
refspec.c
remote.c
repository.c
reset.c
revert.c
revparse.c
revwalk.c
settings.c
sha1_lookup.c
signature.c
socket_stream.c
sortedcache.c
stash.c
status.c
stransport_stream.c
strmap.c
submodule.c
sysdir.c
tag.c
thread-utils.c
tls_stream.c
trace.c
transaction.c
transport.c
tree-cache.c
tree.c
tsort.c
util.c
vector.c
zstream.c
auth.c
auth_negotiate.c
cred.c
cred_helpers.c
git.c
http.c
local.c
smart.c
smart_pkt.c
smart_protocol.c
ssh.c
winhttp.c
xdiffi.c
xemit.c
xhistogram.c
xmerge.c
xpatience.c
..\deps\libgit2\src\transports\winhttp.c(413): warning C4018: '<': Konflikt zwischen 'signed' und 'unsigned' [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\libgit2.vcxproj]
xprepare.c
xutils.c
hash_generic.c
dir.c
error.c
findfile.c
map.c
path_w32.c
posix_w32.c
precompiled.c
pthread.c
utf-conv.c
w32_buffer.c
w32_crtdbg_stacktrace.c
w32_stack.c
w32_util.c
regex.c
libgit2.vcxproj -> C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\Release\libgit2.lib
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(396,5): warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build. [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\zlib.vcxproj]
adler32.c
crc32.c
deflate.c
inffast.c
inflate.c
inftrees.c
trees.c
zutil.c
zlib.vcxproj -> C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\Release\zlib.lib
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(396,5): warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build. [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\http_parser.vcxproj]
http_parser.c
http_parser.vcxproj -> C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\Release\http_parser.lib
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(396,5): warning MSB8029: The Intermediate directory or Output directory cannot reside under the Temporary directory as it could lead to issues with incremental build. [C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\git.vcxproj]
repository.cc
Bibliothek "C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\Release\git.lib" und Objekt "C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\Release\git.exp" werden erstellt.
Code wird generiert.
Codegenerierung ist abgeschlossen.
git.vcxproj -> C:\Users\User1\AppData\Local\Temp\apm-install-dir-116510-12812-4jpq90\node_modules\textual-velocity\node_modules\scandal\node_modules\git-utils\build\Release\git.node

npm WARN optional dep failed, continuing [email protected]
npm WARN engine [email protected]: wanted: {"node":">=0.12"} (current: {"node":"0.10.40","npm":"2.13.3"})
gypnpm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\Users\User1\AppData\Local\atom\app-1.8.0\resources\app\apm\bin\node.exe" "C:\Users\User1\AppData\Local\atom\app-1.8.0\resources\app\apm\node_modules\npm\bin\npm-cli.js" "--globalconfig" "C:\Users\User1.atom.apm.apmrc" "--userconfig" "C:\Users\User1.atom.apmrc" "install" "C:\Users\User1\AppData\Local\Temp\d-116510-12812-11krvu7\package.tgz" "--target=0.36.8" "--arch=ia32" "--msvs_version=2013"
npm ERR! node v0.10.40
npm ERR! npm v2.13.3
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the fs-xattr package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls fs-xattr
npm ERR! There is likely additional logging output above.

C:\Users\User1.atom\packages>apm install fxattr
Installing fxattr to C:\Users\User1.atom\packages failed
Request for package information failed: Not Found
C:\Users\User1.atom\packages>apm install fx-attr
Installing fx-attr to C:\Users\User1.atom\packages failed
Request for package information failed: Not Found
C:\Users\User1.atom\packages>

I have two questions about the currently suggested auto activate code in the init config:

current coffescript:

# Activate package right away
target = document.body.querySelector('atom-workspace')
atom.commands.dispatch(target, 'textual-velocity:start-session')

1. What is the difference between the target using querySelector and the following? and is one more appropriate or recommended by atom?

target = atom.views.getView(atom.workspace)

2. Is there a way to test if there is already an active session in the current atom instance, and not try to start another session each time I open a new window?

Some things that was planned early turned out to not really be needed. After +2 years of usage I believe it overcomplicates the implementation more than it helps. E.g. the service API, which was originally envisioned for a plugin system to allow customizable columns and behavior. In the end it have only used been used internally (AFAIK) for xattrs opt-in behavior (since not supported on all platforms).

Do anyone mind if I remove this and tidy things up? Curious if anyone is actually relying on it.

Created a new file like foobar.txt gets the filename foobar.txt.md. I'm leaning towards having a configuration option to decide what extension to append (if any) if none is provided.

Line 27 from the init.coffee file in recommended usage is throwing an error.

TypeError: atom.packages.getActivePackage(...).mainModule.createView is not a function

This is quite annoying. Tends to happen on two occasions from what I've observed:

• When initial scan finished
  • most likely due to some action changing selected note upon the scan
• After a save and changing editor quickly, jumps back/previews the previously opened note
  • Most likely some race condition and actions, since atom.workspace.open is async. Need to be able to reproduce to pinpoint where the culprit is

Description

Upgraded to the latest release (v0.14.1), on 1.17.0 for atom. On Windows.

Steps to Reproduce

1. Launch textual velocity with hotkey (ctrl + shift + p and select from Start Session from menu)

Expected behavior:
Previously loaded files in location specified in Textual Velocity settings, or default location.
Also could save files to this location.

Actual behavior:

Doesn't load any pre-existing files (.md and .txt).
Also, when trying to save a new file by entering name in search at top and saving, get the following error:
"TestFile.md could not be saved. Error: undefined"

Right now fixed in [title, mdate, cdate], would be nice to be able to change the order, preferrably drag-drop

The current problem is that opening a text-editor (even in pending state) is quite costly, this is an already known issue, atom/fuzzy-finder#5

Considering the preview should focus on text notes, and the goal of the preview is to give a quick glance of the content + matched strings the best solution is probably to implement a minimalistic editor that fulfills the following requirements:

• Preview editor should show content of note
• Highlight matched strings; scroll to first match if outside the visible viewport.
• Upon hitting Enter or focusing on the preview window (e.g. by clicking pane), the editor should be replaced by the default text editor.
• When a note is unselected (e.g. hitting Esc) the preview should be closed.
• Visually it can look similar to the default text editor, but doesn't need all the advanced features (grammar, word wrap etc.), so should be sufficient of rendering a simple HTML element with a note's content.
• Reuse preview when changing selected note.

It would be great if the preview would include syntax styling, most importantly probably markdown.

Steps to reproduce:

1. Select an item or two
2. Write some text in the search field (that doesn't match any existing note)
3. Press enter
4. Save the open text editor of the new note file

Expected behavior:
The file to be saved, and to appear as selected note in the list, and focus to remain in the active text editor.

Actual behavior:
Note appears but is deselected, and instead a preview of the last selected item is opened and set as active pane item.

As proposed in gotjoshua#3 (comment)

I like the behavior that if i search, find and open a note.... then close it again, my focus goes back up to the search (like cmd-L)

I think it's a good idea. That said, perhaps there are others that prefer the current behavior?

Also, meanwhile it's trivial to add in one's init config:

atom.workspace.onDidDestroyPaneItem(function() {
  atom.commands.dispatch(atom.views.getView(atom.workspace), 'textual-velocity:focus-on-search')
})

Vote by thumbs-up/down reaction to this issue, and/or give your opinion if you have something to add.

This is due to the recent release of package file-icons v2, which have significant changes to how the icons are retrieved.

Started happen since sometime around last beta update.

Temporary workaround: create new file in the lowercase and rename it afterwards to uppercase the desired words/characters.

Reporting a bug? Preferrably use the following format:

Prerequisites

• [ x] Are you running the latest version?
• [ x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.

Description

Textual Velocity scans the directory and reads the entire collection anew every single time I start it.

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

Expected behavior: read only changed notes, fast.

Actual behavior: takes about 5 minutes for 8000 notes

Versions

Windows 10 64bit

When a file is selected a preview editor is opened, the matched token should be highlighted so one can quickly determine if it's the wanted file.

The navigate package that I use for inter-file links (filename in brackets) + bracket-match + navigate forward opens filename.txt does not work for me in atom-textual-velocity, unless a project folder is opened in the sidebar. This however considerably slows down the search and everything.
Can you see why that happens?