Giter VIP home page Giter VIP logo

Comments (12)

ikerurda avatar ikerurda commented on May 27, 2024 2
require"telescope".setup {
  ...
  extensions = {
    file_browser = {
      ...
      files = false,
    }
  }
}

from telescope-file-browser.nvim.

ikerurda avatar ikerurda commented on May 27, 2024 2
local open_in_fb = function(prompt_bufnr)
  local action_state = require "telescope.actions.state"
  local Path = require "plenary.path"
  local actions = require "telescope.actions"
  local fb = require("telescope").extensions.file_browser.file_browser

  local entry = action_state.get_selected_entry()[1]
  local entry_path = Path:new(entry):parent():absolute()
  actions._close(prompt_bufnr, true)
  fb { path = entry_path }
end

...
require"telescope".setup {
  ...
  extensions = {
    git_files = {
      mappings = {
        i = { ["<a-e>"] = open_in_fb },
        n = { ["<a-e>"] = open_in_fb },
      }
    }
  }
}
...

This should work, don't know if there's a better way of doing it tho

from telescope-file-browser.nvim.

fdschmidt93 avatar fdschmidt93 commented on May 27, 2024

Does the folder_browser not work for you? See workflow of README and GIF. It's amongst the primary selling points of telescope-file-browser :)

Toggling between file and folder browser is currently mapped by default to <C-f> in insert and f in normal mode, respectively. (Mappings are being revisited, possibly subject to change).

Closing this because I believe it's just an oversight of the README. Let me know in case there's more to do here.

from telescope-file-browser.nvim.

quantum-booty avatar quantum-booty commented on May 27, 2024

@fdschmidt93 thanks I see! Can I make folder_browser the default finder?

from telescope-file-browser.nvim.

quantum-booty avatar quantum-booty commented on May 27, 2024

Also can I select a result from for example require('telescope.builtin').git_files() and open the folder in the file_browser? I guess this is what I had in mind originally.

from telescope-file-browser.nvim.

quantum-booty avatar quantum-booty commented on May 27, 2024

Thanks I think it should be plenary.path instead of plenary.Path, and it only works if the file=true.
But it works!

from telescope-file-browser.nvim.

quantum-booty avatar quantum-booty commented on May 27, 2024

@ikerurda Is it possible to move the cursor on to the file as well?

e.g. I search for telescope in git-files, then open the file_browser.
image
The cursor is on the first line.
image
However it would be nice if it can be placed onto the telescope file directly, like this:
image

from telescope-file-browser.nvim.

quantum-booty avatar quantum-booty commented on May 27, 2024

I think this would be a very nice workflow, worth adding it into the readme.

from telescope-file-browser.nvim.

ikerurda avatar ikerurda commented on May 27, 2024

I've been trying, but haven't found a way of doing it...
Hope somebody can help you :)

from telescope-file-browser.nvim.

fdschmidt93 avatar fdschmidt93 commented on May 27, 2024

I guess what we could add is opting-in that the folder_browser shows one of (i) files (ii) folders or (iii) files and folders and then, whenever one of the three is selected you go to the corresponding folder.

For files, I suppose it makes sense to place the cursor on the selected file.

Once this is natively supported from within the folder browser, I'm happy to add this to the readme.

from telescope-file-browser.nvim.

quantum-booty avatar quantum-booty commented on May 27, 2024

I think it makes more sense to support it as a function rather than another file browser mode, because having it as a functions allows me to open file_browser with various pickers like grep_string and lsp reference.

from telescope-file-browser.nvim.

fdschmidt93 avatar fdschmidt93 commented on May 27, 2024

I think it makes more sense to support it as a function rather than another file browser mode, because having it as a functions allows me to open file_browser with various pickers like grep_string and lsp reference.

Any user is free to customize the extension as they like; that is, such a function is something for the wiki and then everyone can tailor the function to their use case rather than having another action natively. Such an action is not necessarily easy to fit to any picker as information within entries varies across pickers and maybe some users don't want the selected entry to be the file. That's why I prefer something like this for the wiki.

telescope-file-browser should ship with primarily "native" features particular to the extension itself.

For what I elaborated above, having something like this built-in would I guess result in something like #73

E: In any case, I try to add some more information also onto the wiki soon, once better entry display and directory previewer customization lands.

from telescope-file-browser.nvim.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.