Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Discussion forum/IRC channel? #36

Closed
moosingin3space opened this issue Jan 13, 2017 · 7 comments
Closed

Discussion forum/IRC channel? #36

moosingin3space opened this issue Jan 13, 2017 · 7 comments

Comments

@moosingin3space
Copy link
Contributor

GitHub Issues isn't a great platform to discuss major features or ask questions, so it might not be a bad idea to set up another forum/IRC channel for that sort of discussion.
@Wilfred
Copy link
Collaborator

Wilfred commented Jan 14, 2017

Agreed something would be useful. I'd prefer something super low maintenance as I'm mostly writing Rust for Remacs at the moment :). I'm not sure about IRC as it's realtime and we have contributors on all sorts of different timezones. Gitter has scrollback I suppose, but no Emacs integration (AFAIK)!

@moosingin3space
Copy link
Contributor Author

@Wilfred https://github.com/jleechpe/erc-gitter allows you to use Gitter in Emacs (it's how Spacemacs recommends you ask for help).

@shymega
Copy link

shymega commented Jan 30, 2017

IRC can be augmented with logging bots (botbot.me), so it's not really out of the question, IMHO, but others may disagree. We could use Discourse for the forums, and Freenode IRC for the servers..

I'm not the biggest fan of Gitter, Slack, etc. They are not well suited to FLOSS projects, and are non-free, which I don't not like (ethical reasons

WDYT?

@moosingin3space
Copy link
Contributor Author

Discourse might be the best option if realtime isn't desirable.

@shymega
Copy link

shymega commented Jan 30, 2017 via email

@jjrh
Copy link

jjrh commented Apr 4, 2017

Funny - came here looking for where the mailing list or IRC channel was.

As a reader I tend to prefer mailing lists since they allow one to read how ever one likes (web browser archives, emacs, mail client, etc) and as a extension of that allows you to keep track of what you have read.

I like IRC for off the cuff discussion and quick questions (is X implemented, is it known the build from master is failing? etc) Best way to deal with timezones is to just stay connected 24/7 with screen/tmux or a bouncer like ZNC. Understandably that's not a great solution if you're only in one channel.

One project I follow uses google groups as a mailing list and it works reasonably well.

Another uses 'launchpad' https://help.launchpad.net/ListHelp which is so so - issue I have which may be the projects decision is I can't subscribe to it without permission (I mostly want to read it in my mail client or offline - not actually post) They don't have a option to download a mbox or something like say emacs-devel does.

Just my two cents as someone who would subscribe to mostly follow progress.

@Wilfred
Copy link
Collaborator

Wilfred commented Apr 9, 2017

OK, now that Gitter is part of GitLab and will be open sourced, I'm even more inclined to give it a try.

I've created a Gitter room in #167, let's give it a go :).

@Wilfred Wilfred closed this as completed Apr 9, 2017
jeandudey pushed a commit to jeandudey/remacs that referenced this issue May 29, 2017
@npostavs @mina86
Fix ‘!NILP (Vpurify_flag)’ assertion failure during temacs bootstrap
4b3db0d 
The recent changes to src/casefiddle.c cause build failure as seen
below:

    Starting program: /home/npostavs/src/emacs/emacs-bootstrapping/src/temacs
	--batch --load loadup bootstrap
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/usr/lib/libthread_db.so.1".
    Loading loadup.el (source)...
    Using load-path (/home/npostavs/src/emacs/emacs-bootstrapping/lisp
	/home/npostavs/src/emacs/emacs-bootstrapping/lisp/emacs-lisp
	/home/npostavs/src/emacs/emacs-bootstrapping/lisp/language
	/home/npostavs/src/emacs/emacs-bootstrapping/lisp/international
	/home/npostavs/src/emacs/emacs-bootstrapping/lisp/textmodes
	/home/npostavs/src/emacs/emacs-bootstrapping/lisp/vc)
    Loading emacs-lisp/byte-run (source)...
    Loading emacs-lisp/backquote (source)...
    Loading subr (source)...
    Loading version (source)...
    Loading widget (source)...
    Loading custom (source)...
    Loading emacs-lisp/map-ynp (source)...
    Loading international/mule (source)...
    Loading international/mule-conf (source)...

    lread.c:3914: Emacs fatal error: assertion failed: !NILP (Vpurify_flag)

    Breakpoint 1, terminate_due_to_signal at emacs.c:363
    363	  signal (sig, SIG_DFL);
    (gdb) bt
    #0  0x0000000000579826 in terminate_due_to_signal at emacs.c:363
    remacs#1  0x000000000060ec33 in die at alloc.c:7352
    remacs#2  0x000000000066db40 in intern_c_string_1 at lread.c:3914
    remacs#3  0x0000000000576884 in intern_c_string at lisp.h:3790
    remacs#4  0x00000000005dc84f in prepare_casing_context at casefiddle.c:69
    remacs#5  0x00000000005dd37f in casify_object at casefiddle.c:311
    remacs#6  0x00000000005dd47f in Fcapitalize at casefiddle.c:356
    remacs#7  0x00000000006325ac in eval_sub at eval.c:2219
    remacs#8  0x0000000000632368 in eval_sub at eval.c:2184
    remacs#9  0x000000000063446c in apply_lambda at eval.c:2875
    remacs#10 0x00000000006329af in eval_sub at eval.c:2294
    remacs#11 0x000000000062d462 in Fprogn at eval.c:449
    remacs#12 0x000000000062d4cf in prog_ignore at eval.c:461
    remacs#13 0x000000000062f19c in Fwhile at eval.c:982
    remacs#14 0x00000000006321f4 in eval_sub at eval.c:2172
    remacs#15 0x000000000062d462 in Fprogn at eval.c:449
    remacs#16 0x000000000062f0c4 in Flet at eval.c:963
    remacs#17 0x00000000006321f4 in eval_sub at eval.c:2172
    remacs#18 0x0000000000632963 in eval_sub at eval.c:2290
    remacs#19 0x000000000062d462 in Fprogn at eval.c:449
    remacs#20 0x000000000062f0c4 in Flet at eval.c:963
    remacs#21 0x00000000006321f4 in eval_sub at eval.c:2172
    remacs#22 0x0000000000668caa in readevalloop at lread.c:1927
    remacs#23 0x0000000000667253 in Fload at lread.c:1332
    remacs#24 0x0000000000632683 in eval_sub at eval.c:2233
    remacs#25 0x0000000000668caa in readevalloop at lread.c:1927
    remacs#26 0x0000000000667253 in Fload at lread.c:1332
    remacs#27 0x0000000000632683 in eval_sub at eval.c:2233
    remacs#28 0x0000000000631be5 in Feval at eval.c:2041
    remacs#29 0x000000000057e1af in top_level_2 at keyboard.c:1121
    remacs#30 0x000000000062ffc7 in internal_condition_case at eval.c:1324
    remacs#31 0x000000000057e1f0 in top_level_1 at keyboard.c:1129
    remacs#32 0x000000000062f51e in internal_catch at eval.c:1091
    remacs#33 0x000000000057e0ea in command_loop at keyboard.c:1090
    remacs#34 0x000000000057d6d5 in recursive_edit_1 at keyboard.c:697
    remacs#35 0x000000000057d8b4 in Frecursive_edit at keyboard.c:768
    remacs#36 0x000000000057b55b in main at emacs.c:1687

    Lisp Backtrace:
    "capitalize" (0xffffcf70)
    "format" (0xffffd130)
    "define-charset" (0xffffd370)
    "while" (0xffffd560)
    "let" (0xffffd7c0)
    "dolist" (0xffffd910)
    "let" (0xffffdb70)
    "load" (0xffffdfe0)
    "load" (0xffffe4a0)

* src/casefiddle.c (syms_of_casefiddle): Declare four new symbols:
Qtitlecase, Qspecial_uppercase, Qspecial_lowercase and
Qspecial_titlecase.
(prepare_casing_context): Use aforementioned symbols.
@cbbrowne cbbrowne mentioned this issue Nov 23, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Wilfred @moosingin3space @jjrh @shymega