Code Monkey home page Code Monkey logo

nameframe's People

Contributors

john2x avatar syohex 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  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

nameframe's Issues

Projectile + nameframe

I've tried setting up name frame in different configurations (mostly using use-package). Right now I can see that in fact:

projectile-before-switch-project-hook's value is (nameframe-projectile--before-switch-project-hook)

but it does not seem to work. When switching projects using projectile-switch-project it continues to re-use the same frame, always.

name frame-create-frame works and opens the currently active buffer in a new frame.

Make nameframe work with helm

Readme states that nameframe will not work with helm which I can see now. Do you know why or where to start looking to add such support?

I can see that after a frame was created, the keyboard input focus is still on the original frame...? At least on first interaction. Also, helm's buffer seems to stay open after selecting a project.

If I try to press Meta X in the newly created frame (after opening a project with projectile, with perspective enabled as well) I can see this messages:

persp-switch: Marker points into wrong buffer: #<marker in no buffer>
Aborting an helm session running in background

Respect frame-title-format

When creating frames with the name property specified, the name is used as the title (ignoring frame-title-format.

It would be nice if the frame-title-format is still followed, so that a frame-title-format of "[%F] %b" would allow a more descriptive frame title.

[Enhancement] next/previous-buffer per frame

I am trying to get a frame based workflow working. I work mostly in terminal and want to open frames which dont share buffers with other frame. Nameframe seems to work as I want when I use ivy.

I want to override the next/previous-buffer for fast switching buffers per frame. Right now it shows buffers of all frames.

I have the below config.

(use-package nameframe
  :defer t
  :after projectile perspective
  :init
  (persp-mode)
  (nameframe-projectile-mode t)
  (nameframe-perspective-mode t)
  )

dired, magit etc

I was wondering how we can make this work were e.g. all dired buffers would be grouped together (all dired buffers into one buffer, possibly having to use perspective).

Any clue how?

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.