Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 09:55

    xiaq on master

    cliedit: edit:smart-enter accep… (compare)

  • 09:40
    SolitudeSF commented #877
  • 09:32
    epikur-io edited #877
  • 09:26
    epikur-io opened #877
  • Dec 14 16:44
    xiaq closed #627
  • Dec 14 16:44
    xiaq commented #627
  • Dec 14 16:42

    xiaq on master

    cliedit: Fix crash when edit:li… (compare)

  • Dec 13 22:36

    xiaq on cliedit

    cli/addons/listing: Set ExtendS… cliedit: Support passing a quer… (compare)

  • Dec 13 10:09

    xiaq on cliedit

    cliedit: Add edit:listing:start… (compare)

  • Dec 12 21:25

    xiaq on cliedit

    cli: Add utils for getting and … cli/addons/listing: New addon f… (compare)

  • Dec 09 13:32
    chengxuncc commented #789
  • Dec 09 13:27
    chengxuncc commented #789
  • Dec 09 13:24
    chengxuncc commented #789
  • Dec 09 10:30

    xiaq on master

    fix [archlinuxcn] instructions … (compare)

  • Dec 09 10:30
    xiaq closed #875
  • Dec 09 10:30

    xiaq on master

    [#873] fix json output of -comp… (compare)

  • Dec 09 10:30
    xiaq closed #874
  • Dec 09 10:29
    xiaq commented #874
  • Dec 09 06:22
    chengxuncc edited #876
  • Dec 09 06:22
    chengxuncc edited #876
mesajor
@mesajor
[xiaqqaix] Going to merge the cliedit branch into master now that edit:listing:start-custom is a (mostly) viable replacement for edit:
[xiaqqaix] (cont.) edit:-narrow-read.
[Ian] 🚀
[Ian] I haven't been paying too much attention, is this supposed to be a breaking change for anything?
[xiaqqaix] If you have already been using the cliedit branch, no breaking change for you
[xiaqqaix] If you haven't, there are some breaking changes...
mesajor
@mesajor
[Ian] I have not
[Ian] It's exciting living on the edge, but I've been too busy to be excited
[xiaqqaix] heh :)
[xiaqqaix] i made a list of functions and variables that were removed from the edit: module, honestly there are just a few...
[xiaqqaix] i will prepare a proper release note, but in the meanwhile, i'd encourage you to give it a try and see what breaks 😉
[Ian] If you put it in the commit message (if it's not too much) I'll get a lovely notice every time i open a new shell until i upgrade
[xiaqqaix] it's a lot of changes on a separate development branch unfortunately, and the commit message is just "merge branch cliedit"
[Ian] haha
[Ian] oh well
mesajor
@mesajor
[Ian] ah, that's why my tool is breaking, github is taking too long to process all the commits or something
mesajor
@mesajor
[Ian] Ok, updated, edit:styled is replaced?
[SolitudeSF] with just styled
[SolitudeSF] elves/elvish#627 can be closed
[Ian] Is there a reference doc for styled now?
[Ian] oh right, not under edit anymore
[Ian] heh
mesajor
@mesajor
[SolitudeSF] so, how do i assign a result of edit:listing:start-custom to a variable?
[SolitudeSF] not providing accept argument crashes the shell
[Ian] Is styled limited to the 16 named colors?
mesajor
@mesajor
[xiaqqaix] Clarify what the "result" is? (re @SolitudeSF: so, how do i assign a result of edit:listing:start-custom to a variable?)
[SolitudeSF] the value i chose? im not sure about structure of arguments supplied.
[xiaqqaix] Supply the accept callback then
[xiaqqaix] listing:start-custom just starts the listing; it does not block until you choose an item, so it cannot output the value you chose
[SolitudeSF] im stuggling with that
[SolitudeSF] can you give an example for sub 80 iq people?
[xiaqqaix] Like this: accepted = ''; listing:start-custom $items &accpet=[a]{ accepted = $a }
[SolitudeSF] ah
[xiaqqaix] Fixed (re @SolitudeSF: not providing accept argument crashes the shell)
[xiaqqaix] Yes, for the moment... (re @Ian: Is styled limited to the 16 named colors?)
mesajor
@mesajor
[SolitudeSF] ok, so there is no way to emulate blocking behavior?
mesajor
@mesajor
[xiaqqaix] Nope
mesajor
@mesajor
[Ian] how unfortunate 😄 (re @xiaqqaix: Yes, for the moment...)
[Ian] Anyone want to recommend a theme with git info that only uses named colors?
[Ian] My custom one went a bit overboard and has...a lot of colors
[xiaqqaix] Or I can implement support for 256 colors :)
mesajor
@mesajor
[xiaqqaix] The part I'm struggling with is naming in an unambiguous way; I want "styled" to be a very generic construct and applicable to (say) a web front-end in future
mesajor
@mesajor
[Ian] There is this...but it's not perfect: https://jonasjacek.github.io/colors/
mesajor
@mesajor
[xiaqqaix] I don't intend to implement the "xterm names"; rather I am thinking of a scheme that can distinguish colors from the xterm 256-color palette from other palettes. For example, calling a color "color17" or "navyblue" does not convey which palette it is from. Calling a color "xterm256/17" or "xterm256/navyblue" does, but is way too verbose. (re @Ian: There is this...but it's not perfect: https://jonasjacek.github.io/colors/)
[xiaqqaix] I guess I will settle on "xterm$n", eg "xterm17"
mesajor
@mesajor
[dakinflo] may I ask is there something like this? I really don't want to type ⬆️.: http://b.xiaq.me/a39f5e70/file_3342.jpg
[dakinflo] may I ask is there something like this in elvish modules? I really don't want to type ⬆️.: http://b.xiaq.me/a39f5e70/file_3342.jpg
mesajor
@mesajor
[SolitudeSF] there isn't
mesajor
@mesajor
[dakinflo] oh great I think I can write one.