Code Monkey home page Code Monkey logo

feebleline's People

Contributors

dickby avatar endian-benjamin avatar jcs090218 avatar kevinboulain avatar kungsgeten avatar rgiar avatar tautologyclub avatar wilfred 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  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  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

feebleline's Issues

License missing

This may be a small catch, but it's very important to include the GPL license for emacs packages in the header or additionally in the repository itself sometimes.

Wrong project name.

If you enter a project then go back to a temporary buffer like *scratch*, *dashboard*, etc. The project name remained.

Showing time

You have deleted feebleline-show-time option at a98f799 in development branch. Is it possible to show time in the latest version of the development branch? If not, is there any reason why you deleted the option?

List of 'recipes' for feebleline-mode-text?

It's nice that feebleline-mode-text is easily customizable, but shouldn't it be built on some kind of list of functions and modifiers for easier modification?

Actually, it seems the way to edit/extend is to simply copy/paste it into your Emacs configuration and add or remove some parts of it.
Should the format be revised to allow people to make pull requests to your repository and add some functions that add more information (without necessarily adding them to the default value)?

For example, if I want to make a pull request to add Circe support so others don't have to find their way around, I would have to append it to the list and it will continue to grow and may be difficult to get it right (for example, the fact that I didn't want some spaces between some of the information require to copy most of the definitions, see for example the colon between the file and the git branch in #24 which differs from the default value). Also, since I have to redefine the whole variable, I can't even use some of the definitions from your repository.

Screenshot for the Circe support:
screen shot 2018-09-30 at 18 38 38
You can see some some channels:

  • I'm actually visiting #bla so it's marked like a standard buffer
  • I have been highlighted in #blu so I took the asterisk face you have setup and appended it to the channel's name
  • #bli has some discussion in it but there is nothing special (no highlight) so it's a bit more dim
  • other channels are not listed for concision since there isn't any activity in them

Off the top of my head (I'm no Elisp expert so take it with a grain of salt), here is a proposition that could probably resolve this issue and ease contributions and customization (not tested, so may contain typos):

(setq feebleline-mode-line-text
      '(;; after would optionally add the space if something after it evaluate to a non-empty string
        (line-and-column-number :face feebleline-linum-face :after " ")
        ;; before (I lack a better name) is tricky, but should have some mechanism to places its string before the previous :after property?
        (buffer-name :face feebleline-dir-face :after " ")
        ;; when the function may return nothing, simply ignore before/after properties
        (git-branch :face feebleline-git-branch-face :before ":" :after " ")
        ;; no special face because it will use multiple ones for the same string
        (circe-channels)))

Thanks!

`git` branch display doesn't work on tramp-mode

The git branch display doesn't work when working on a remote git repository using Tramp mode. Instead of showing branch it displays error like this: cd: no such file or directory: /ssh:user@host:/path/to/file

I think code over here[1] needs to be more clever. Not sure how other plugins work with Tramp, but most other things (like vc-mode, magit) work. Maybe we can reuse something from vc-mode to identify the repository branch? That way it can also work other version control systems as well.

[1] https://github.com/tautologyclub/feebleline/blob/master/feebleline.el#L124

feebleline error: (wrong-type-argument stringp (Git ~/emacs/))

I'm not sure this is consequential, but I'm also getting a feebleline related segfault, tracked here, which implicates feebleline:

bug#56869

I wonder if these are related. The backtrace I get is:

Lisp Backtrace:
"call-process" (0xf14502f0)
"call-process-shell-command" (0xf1450248)
"shell-command" (0xf14501e0)
"shell-command-to-string" (0xf1450190)
"feebleline-git-branch" (0xf1450148)
"feebleline--insert-func" (0xffffb1b8)
"apply" (0xf14500e8)
"feebleline--insert" (0xf14500a8)
"feebleline--insert-ignore-errors" (0xf1450058)
"apply" (0xf1450050)
"timer-event-handler" (0xffffc608)
1789	in ../../../../../gdk/x11/gdkdevicemanager-xi2.c

could each frame have its own feebleline?

Currently all the frames will have the same feebleline, for example, all feebleline will show the same filename. I think this could be related to those feebleline functions.

Bottom (horizontal) window divider not showing

I suspect this isn't a feebleline thing but is probably something to do with window-divider-mode but I'm hoping you might be able to help.

I'm using GNU Emacs 25.3.1 on MacOS, and I've installed with:

(use-package feebleline
  :ensure t)

And I have vertical border between horizontal windows, but not a horizontal divider between vertical ones:

screen shot 2018-02-26 at 18 37 13

window-divider-mode is on (presumably enabled by feebleline) and I've tried playing around with the window-divider-default-bottom-width, window-divider-default-places to no avail. Weirdly I see the vertical border regardless of the state of window-divider-mode, so perhaps there's another way to draw the borders I'm not aware of. It also doesn't seem to matter which theme I select, as I thought perhaps it was a bad face definition.

Love how feebleline looks so really hoping I can figure this out!

Breaks visual-regexp.el

Gotta say, I love the minimal look & feel of feebleline! I'd love to keep using it, but unfortunately I need visual-regexp to work since I use it a couple of dozen times a day.

Here's the problem: when I run vr/replace I should see inline a list of candidates:

Screen Shot 2021-01-25 at 20 42 51

And then when I hit enter, I should see the replacement as it will be entered:

Screen Shot 2021-01-25 at 20 43 36

However, if I activate feebleline-mode and run through the same process, at first I don't see any matches at all:

Screen Shot 2021-01-25 at 20 45 10

But it actually has found some matches, because if I hit enter, I see this:

Screen Shot 2021-01-25 at 20 45 42

It looks like it's displaying some weird mini buffer contents.

Any ideas how I could work around this to keep feebleline?

don't use custom-set-*

If variables/faces are set with custom-set-* they get written to the 'custom-file' if that is non-nil.

All-the-icons support

Hi, is it possible to add some icons to feebleline? Major mode icon, modified indicator etc?

emacs 26 breaks feebleline

I believe changes to the advice interface messes stuff up for feebleline in emacs 26. OTOH, I don't think feebleline has any use for it anymore, it was more of a leftover from early versions of feebleline. Will push a fix to master.

Horizontal border in terminal?

Hi there,

Since the mode line seems to be the go-to horizontal separator between buffers, when feebleline is active there isn't much visual clues to know where a buffer ends and where another starts.
Vertically, everything is fine since there is the vertical border.

It's probably related to #10 but since my Emacs is always started from a terminal, I can't seem to rely on window-divider-mode.

I attach some screenshots to better to showcase the problem.

First, the *scratch* buffer with a vertical split (I wrote some stuff in the buffers as an explanation):
screen shot 2018-09-30 at 17 49 07

Then I split the left window horizontally and open /tmp/feebleline.txt:
screen shot 2018-09-30 at 17 54 45

Notice that due to mode-line-format being buffer-local, I can't seem to get rid of the right mode line activated by the top left window (since I want a visual separator between *scratch* and /tmp/feebleline.txt.

Of course, I could somehow cheat with line numbers and convince myself it's enough of a visual clue but it's bit cumbersome when the number have similar digits (even more for multiple horizontal splits):
screen shot 2018-09-30 at 18 20 43

Do you see any way to solve this small issue? I'm sure I can live with it but well, if I could make it perfect... :)
Or maybe I should dim the inactive windows (but it's probably a bit hard to make it play well with all themes out of the box?).

By the way, here is the Elisp hack shown in the first two screenshots, sorry for my awful Emacs-fu :)

(add-hook 'window-configuration-change-hook
          (lambda ()
            (when (bound-and-true-p feebleline-mode)
              (walk-windows (lambda (window) ; reset the mode line of each buffer
                              (with-current-buffer (window-buffer window)
                                (setq mode-line-format nil)))
                            0) ; don't include minibuffer
              (walk-windows (lambda (window) ; and set the mode line when necessary
                              (with-current-buffer (window-buffer window)
                                ;; {frame,window}-edges functions return (x1 y1 x2 y2)
                                ;; then check if the current buffer (which may be displayed on mutltiple windows)
                                ;; doesn't sit on top of the minibuffer
                                ;; this isn't perfect but unfortunately, the mode-line-format is buffer-local
                                (when (/= (nth 1 (window-edges (minibuffer-window)))
                                          (nth 3 (window-edges window)))
                                  (setq mode-line-format "%-"))))
                            0))))) ; don't include minibuffer

The idea is simple: use a dumbed down mode line as an horizontal separator if and only if a window doesn't sit on top of the minibuffer.

Thanks for the package :)

Regards.

feebleline-project-name doesn't align to the right.

as title.
Image 1

Image 2

Should [pokerapp] be on the right?

My config below.

(use-package feebleline
  :defer t
  :config
  (setq feebleline-msg-functions
        '((feebleline-line-number :fmt "%5s" :post "")
          (feebleline-column-number :pre ":" :fmt "%-2s")
          (feebleline-file-directory :face feebleline-dir-face :post "")
          (feebleline-file-or-buffer-name :face font-lock-keyword-face :post "")
          (feebleline-file-modified-star :pre " " :face font-lock-warning-face :post "")
          ;;(feebleline-git-branch :face feebleline-git-face :pre " : ")
          (feebleline-project-name :pre "[" :align right :post "]")
          )))

Concealing helm modeline

I noticed that the modeline in helm isn't hidden when I open a Helm buffer, and I couldn't find discussion about how to conceal it. To be clear, I'm talking about the bottom modeline that Helm makes that's wedged between the helm buffer and the minbuffer. It's pretty conspicuous in an Emacs frame that's otherwise perfectly, wonderfully modeline-free. There's that thread on Emacs StackExchange that looks like it has something to do with this, which is why I was so confused when I evaluated some of the snippets in that thread, but actually reading the code that I so stupidly evaluated, I realized that they (or maybe I'm just mistaken) were trying to conceal the top modeline above the header. So back to square one.

Sorry if this is actually a known, easily-amended thing with Helm that I just don't know about. But you probably know how the documentation situation is with Helm, just by sheer nature of being so featureful.

Share your screen shots!

If you want to show off how nice their (lack of) mode-line looks using feebleline, I'd love to see scrots. I'll post them in the README.md so the whole world can see.

warning while startup

with an .emacs that only contains:

(package-initialize)
(require 'feebleline)
(feebleline-mode)

I get the following warning at startup:
Warning (bytecomp): reference to free variable ‘ad-do-it’

I use:
GNU Emacs 27.0.50 (build 41, x86_64-pc-linux-gnu, GTK+ Version 3.22.26) of 2018-02-07

Way to enable resizing of minibuffer window?

I tried to (setq resize-mini-windows t) and remove the (message-truncate-lines t) & (max-mini-window-height 1) but the minibuffer is still fixed to one line height.
I also tried to window-resize during feebleline--insert but it will mess up some interaction.

Sometimes I get a long line to display and would like to avoid the truncation (I don't use the right alignment).
Any idea?

Support active/inactive color

Hi, your plugin is awesome, i have use it instead my https://www.emacswiki.org/emacs/MiniBufferTray

It will be cool if this plugin support active/inactive color like below:

(custom-set-faces
 '(mode-line ((t (:background "darkred" :foreground "darkred" :height 0.1))))
 '(mode-line-inactive ((t (:background "gray10" :foreground "gray10" :height 0.1))))
)

I have test above code after load feebleline plugin, but active color won't work.

With new update nothing is shown

Hey,

I just have updated the feebleline. I am using the new configuration (from the readme):

(use-package feebleline
:ensure t
:config (setq feebleline-msg-functions
'((feebleline-line-number :post "" :fmt "%5s")
(feebleline-column-number :pre ":" :fmt "%-2s")
(feebleline-file-directory :face feebleline-dir-face :post "")
(feebleline-file-or-buffer-name :face font-lock-keyword-face :post "")
(feebleline-file-modified-star :face font-lock-warning-face :post "")
(feebleline-git-branch :face feebleline-git-face :pre " : ")
(feebleline-project-name :align right)))
(feebleline-mode 1))

feebleline mode is enabled. However nothing is shown in minibuffer. Could you help me to find what is the problem.

Doesn't play nice with TRAMP

On one Emacs I have Error running timer ‘feebleline--insert’: (file-error "Process has died") which completely hides TRAMP's password prompt.
On another it totally make Emacs responsive (or crashes it) :)

I simply run something similar to emacs /ssh:root@localhost:/, no special configuration.

Conditional branch color

Hi, it would be really nice if the color of the VC branch name could be set according to the branch. I have a feeling that it's already possible, I tried something like this

(setq feebleline-git-face (if (eq (magit-get-current-branch) "master") 'warning 'feebleline-git-face)) and while it evals without error, it doesn't work.

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.