Git Product home page Git Product logo

telescope-tasks.nvim's People

Contributors

hgigas avatar lpoto avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

Forkers

hgigas mslauson

telescope-tasks.nvim's Issues

Output window footer

Since floating windows now support footers, it would be useful to display the command being run in the footer (if a float is being used for displaying the output in a separate window)

Multiple commands

Tasks should be allowed to contain a table of commands instead of just a single command.

  • The added commands should go to the same cmd field, but instead each command should have a string key and a string or a table value, so the different commands may be identified with their own names, and the multiple command value may be distinguished from the single command value.
  • When multiple commands are added, before running the task, a user should select the command they want to run in a popup.

Example

cmd = {
  run = {"go", "run", "."},
  build = {"go", "build", "."}
}

When executing a task with such value the user would be then prompted with a popup containing the lines:

run
build

Generator startup

Is there any way to run a command on each file when the generator generates a task during startup? I'd like to have persistence by having it reconnect to a tmux session if it exists.

Running current file

Add default generators that run the current file. For example, a generator should check whether the current file contains a main function, and generate a task for running it, if it does (this would be useful for filetypes such as c, c++, java).

Something like this is currently already implemented for Go default generators
(It generates a task for a file only if it contains main package and main function), and for Lua.

feat: new key mapping for (not) "changing the command before running the task"

Now there is lock task spec to (not) allow changing the command before running the task but sometimes you want to edit the command sometimes you don't want.

An option to allow changing the command sometimes is, for example, Return run the command without changing it, Ctrl-Return allow changing the command before running.

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.