Package Details: caret-bin 3.4.6-1

Git Clone URL: https://aur.archlinux.org/caret-bin.git (read-only)
Package Base: caret-bin
Description: Premium Markdown Editor http://caret.io
Upstream URL: https://github.com/careteditor/caret
Licenses: unknown
Submitter: Sasasu
Maintainer: Sasasu (manuel)
Last Packager: Sasasu
Votes: 8
Popularity: 0.001241
First Submitted: 2016-12-26 15:59
Last Updated: 2018-06-06 05:36

Latest Comments

1 2 Next › Last »

mthomas commented on 2018-06-11 14:57

Sasasu:

That's great - thank you! I get a complaint about the pkgver having a hyphen in it, but other than that it works great.

Sasasu commented on 2018-06-11 09:41

mothomas:

confirm.

they move caret to /usr

new PKGBUILD here: https://gist.github.com/Sasasu/faeae01662b194f2e9097ff6843d3c90

and in after-install.tpl they still assume the executable file is /opt/caret-beta/caret-beta

I think Debian user can not launch caret using terminal :)

and LICENSE is MIT, interesting.

mthomas commented on 2018-06-10 22:09

Sasasu: The beta packages are on a separate page: https://github.com/careteditor/beta/releases/tag/4.0.0-rc8. Also - trying your suggestion for modified pkgbuild is giving me:

cp: cannot stat 'opt/caret/*': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

Sasasu commented on 2018-06-06 05:25

tridnguyen:

I didn't find 4.0 bate in release page. if you have a file named "caret-4.0-bate.deb"

modify PKGBUILD.

pkgver=4.0-bate
source=("$PATH_TO_DEB_FILE")
md5sums=('SKIP')

then use makepkg to build an arch package.

tridnguyen commented on 2018-06-06 04:45

Can this be updated to include the 4.0 beta versions?

cweagans commented on 2018-06-05 18:54

Looks like the yay AUR helper has some trouble with PKGBUILDs that don't end in a newline. Can you add a newline please?

Ref https://github.com/Jguer/yay/issues/469

manuel commented on 2017-05-06 11:25

I just tried multiple parameters with another editor and they are expanded correctly: Caret looks like doesn't support multiple filenames on the command line btw, but trying the script with Geany works fine.

A softlink should work fine, not sure about the AUR stance on this btw..

Sasasu commented on 2017-05-06 10:55

well...
In zsh the auto-complete will complement the file name by "\ "
if there many files to open, using double quotes maybe not work as expect..

Maybe i should use a soft link? not a script.

manuel commented on 2017-05-06 10:47

Ops, looks like the argument expansion lacks wrapping in double quotes, this way filenames containing spaces won't open either :)

manuel commented on 2017-05-06 10:43

Thank to you Sasasu, for taking the time to maintain this and for fixing it!