Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Tassilo Horn
    @tsdh
    micah:madduck.net: Yeah, the initial sync can take a while. I think you see "Fetching page i/X" messaged every now and then.
    2 replies
    micah
    @micah:madduck.net
    [m]
    Ok, I did try that and re-did the pull and it seems to still get stuck on the same issue :9
    micah
    @micah:madduck.net
    [m]
    I've turned on toggle-debug-on-error and am re-doing it, in the hopes I could find more details
    micah
    @micah:madduck.net
    [m]
    hmm, this time it got stuck at a different number, with no errors produced
    micah
    @micah:madduck.net
    [m]
    ok, it doesn't seem to be progressing
    four hours later, its still stuck at 871/1936 -- is there some debugging I can do here?
    micah
    @micah:madduck.net
    [m]
    ok, i've tried again and finally got to the bug, which appears to be magit/ghub#81
    hpfr
    @hpfr:matrix.org
    [m]
    @tarsius: what do you think about setting a new default prefix for annex so as not to conflict with forge?
    oops, maybe that's a question for kyle meyer
    should I open an issue
    Ag Ibragimov
    @agzam
    Is it possible to have "hidden" keys (suffixes) within magit-transient?
    I'd like to be able to press keys and invoke actions, but not have them shown in the transient
    10 replies
    Ag Ibragimov
    @agzam

    @tarsius, or maybe someone else who knows the answer. I have another question related to transient.el.

    Is it possible to add some arbitrary elements to a transient?
    Not related to keys at all, just some text?
    I want to use a transient as a HUD, to display some random info.

    Jonas Bernoulli
    @tarsius
    Yes. Just use the string in any place you could use a suffix.
    Ag Ibragimov
    @agzam
    Cool, I'm gonna try that. Oh boy, transient.el is very nice. I wish I tried it out sooner.
    alphapapa
    @alphapapa:matrix.org
    [m]
    That reminds me, I need to add Transient dialogs to Ement.el.

    This message is replying to a Matrix event but we were unable to find associated bridged Gitter message to put it in the appropriate threaded conversation.

    I don't think there's a macro for it, but you could do (lambda (&rest _args) 42)

    hpfr
    @hpfr:matrix.org
    [m]
    is there a way to get the status buffer to stop warning me about no newline at the end of symlink files?
    hpfr
    @hpfr:matrix.org
    [m]
    or is there a way to configure this for git diff, since I'm guessing that's where magit gets it
    Tassilo Horn
    @tsdh
    hpfr:matrix.org: I guess the file being the target of the symlink is missing a final newline. Why not just fix that?
    hpfr
    @hpfr:matrix.org
    [m]
    I believe it's referring to the symlink itself. I'm committing the symlink
    Tassilo Horn
    @tsdh
    hpfr:matrix.org: And the source of the symlink is not in the repository?
    hpfr
    @hpfr:matrix.org
    [m]
    correct. I'm using git-annex, so it's a binary file I don't want in the repo directly
    Tassilo Horn
    @tsdh
    Hm, I don't know how git handles symlinks to external files. I'd assume just as symlinks to files in the repo itself. But a symlink shouldn't have newline problems. Did you check if core.symlinks is true in your repo? If not, symlinks are converted to text files containing the path of the target (a workaround for file systems without real symlinks).
    hpfr
    @hpfr:matrix.org
    [m]
    @tsdh: core.symlinks is true, I can open the symlinked files just fine in the working tree. the mime encoding is binary and the mime type is inode/symlink
    Tassilo Horn
    @tsdh
    hpfr:matrix.org: I've just tried to reproduce with an repo-internal symlink but got no warning in the status buffer in the first place although at least the symlink target file is missing a final newline. I only see "\ No newline at end of file" in the diff buffer on commit.
    hpfr
    @hpfr:matrix.org
    [m]
    I guess this is really a git diff issue, but since you're trying to reproduce, I see it in all cases (the diff engine does the same thing for all of them anyway, so idk how that happened to you)
    mkdir -p ~/tmp/git-symlink-no-newline
    cd ~/tmp/git-symlink-no-newline
    git init
    touch test.txt
    ln -s test.txt link.txt
    git add *
    # these both show it
    git diff --cached
    emacs --eval '(magit-status)'
    git commit -m "Test git diff symlink no newline issue"
    # so do these
    git show HEAD
    emacs --eval '(magit-show-commit "HEAD")'
    Tassilo Horn
    @tsdh
    Ah, allright, I can confirm. :-)
    So indeed symlinks are displayed in the git diff as files containing the target file name without newline.
    Ag Ibragimov
    @agzam

    I'm scratching my head and can't figure out this one.
    I have a transient with two similar functions:

    (defun frame-width-shrink ()
      (interactive)
      (set-frame-width nil (- (frame-width) 5)))
    
    (defun frame-width-widen ()
      (interactive)
      (set-frame-width nil (+ (frame-width) 5)))
    
    (transient-define-prefix frame-size-transient ()
      [("H" "shrink frame width" frame-width-shrink :transient t)
       ("L" "widen frame width" frame-width-widen :transient t)])

    It looks totally fine, right? But my conundrum is that for some reason, widening works while shrinking doesn't. Calling the command manually - works. Evaling it - also works. If I make it ("H" "shrink frame width" frame-width-shrink :transient nil) - it works. But I need it to be transient.

    Can someone think of a reason why wouldn't it work? Specifically, it doesn't work when invoked from the transient popup. Everywhere else - it works.

    Ag Ibragimov
    @agzam
    That looks like that has something to do with the frame. It just can't shrink when transient popup is shown. All my attempts to temporarily hide the transient, shrinking the frame, and then showing the transient again were not successful. Can't figure this out
    Ag Ibragimov
    @agzam
    Oh, I think I solved that. I've added (quit-restore-window transient--window) just before (set-frame-width ...). Looks like that did the trick
    Jake Goulding
    @shepmaster
    Is there a way to disable the with-editor usage message (Type C-c C-c to finish, or C-c C-k to cancel) when entering rebase mode? I do this from the command line and my first keystroke is eaten up by dismissing that message.
    3 replies
    alphapapa
    @alphapapa:matrix.org
    [m]
    And do you mean that it happens in a terminal, but not in a GUI Emacs?
    Jake Goulding
    @shepmaster
    I hadn't thought to test it with the GUI mode, but it does appear to be different there.
    I've got one emacs server running and use it from the command line and the GUI
    I just have my EDITOR set to stay in the terminal.
    Jake Goulding
    @shepmaster
    Hmm. And now I can't reproduce it (this is something that's plagued me for years, so I know it's gonna come back)
    alphapapa
    @alphapapa:matrix.org
    [m]
    shepmaster (Jake Goulding): Seems like more of an Emacs issue than a Magit issue, since it would affect anything that did what Magit does AFAIK.
    Jake Goulding
    @shepmaster
    hmm, alright then. As part of my debugging, is there an answer to my original question ("disable the with-editor usage message")?
    1 reply
    gonewest818
    @gonewest818:matrix.org
    [m]
    I’m working on a project that happens to be developed on Windows 10, and it’s reminding me how slow magit can feel on Windows… what’s the current thinking on optimizing magit for Windows?
    1 reply
    JJ
    @jj:feneco.party
    [m]
    is there a way to get the "files changed" from a pull request in github into magit? the workaround I found to get what I wanted was to use get to the log screen (l l), select the commits I want and get the diff (d). I'm reading through Forge manual to see if it has that option, but if someone knows how I could get that info, ideas are welcome. thanks!
    JJ
    @jj:feneco.party
    [m]
    I guess this answers my question: magit/forge#217
    Carl Dong
    @dongcarl
    Hi all, I'm trying to learn more magit to switch over from my CLI workflow. I often do git rebase -i (git merge-base origin/master HEAD) in order to edit commits since branch-off from master but without rebasing over new commits on master. Wondering if there's something similar in magit?
    peddie
    @peddie:matrix.org
    [m]
    @dongcarl: can you use r i and select the merge base in the list?
    Carl Dong
    @dongcarl
    Good point, wish there were a way to have magit figure that out but I guess I can edit magit's source
    peddie
    @peddie:matrix.org
    [m]
    @dongcarl: magit already has a way to work out the commit you're looking for when you call b s, I think. so it might be an easy change
    gonewest818
    @gonewest818:matrix.org
    [m]
    If you’ve already selected a commit in “recent commits”, or in the magit log (l l or l b), then rebase interactive (r i) uses that commit. Granted, it doesn’t figure out the common base automatically.
    JJ
    @jj:feneco.party
    [m]
    hi, how can I set the magit status buffer to revert automatically when I commit something? currently when I commit something, I have to press g to get the magit status buffer updated. the magit-auto-revert mode is enabled in my config. any ideas here? thanks!
    JJ
    @jj:feneco.party
    [m]
    it seems that should be the default with magit-refresh-status-buffer but it doesn't seem to be working for me
    JJ
    @jj:feneco.party
    [m]
    it seems that it doesn't happen with all repos, so maybe a pre commit hook is causing this