1 |
On 10/06 11:06, Randolph Maaßen wrote: |
2 |
> You might be interested in got hooks [1], especially the post-checkout hook. |
3 |
> |
4 |
> I would try to automatically recompile the md-> HTML on every checkout, so |
5 |
> the HTML is up to date after pulling |
6 |
> |
7 |
> [1] https://git-scm.com/book/gr/v2/Customizing-Git-Git-Hooks |
8 |
> |
9 |
> Am Sa., 7. Okt. 2017, 00:58 schrieb Anton Molyboha < |
10 |
> anton.stay.connected@×××××.com>: |
11 |
> |
12 |
> > On Fri, Oct 6, 2017 at 6:49 PM, R0b0t1 <r030t1@×××××.com> wrote: |
13 |
> > |
14 |
> >> On Fri, Oct 6, 2017 at 5:41 PM, <tuxic@××××××.de> wrote: |
15 |
> >> > On 10/06 05:49, Andrew Tselischev wrote: |
16 |
> >> >> On Fri, Oct 06, 2017 at 07:07:04PM +0200, tuxic@××××××.de wrote: |
17 |
> >> >> > Hi, |
18 |
> >> >> > |
19 |
> >> >> > The u8g8lib, which contains libraries to drive a great amount of |
20 |
> >> >> > displays for mainly embedded electronics has a wiki on github, which |
21 |
> >> >> > can be oficially git-pulled as a local copy...which I did. |
22 |
> >> >> > |
23 |
> >> >> > Now I have tons of *.md (markdown) -files instead of html and I |
24 |
> >> >> > dont know of any handy viewer for these. |
25 |
> >> >> > |
26 |
> >> >> > Since I want to update the repo from time to time |
27 |
> >> >> > I dont want to convert them. |
28 |
> >> >> > |
29 |
> >> >> > Is there any recommended quick and clean way to view these files on |
30 |
> >> the fly as |
31 |
> >> >> > they would be html? |
32 |
> >> >> > |
33 |
> >> >> > Thanks a lot for any help in advance! |
34 |
> >> >> > Cheers |
35 |
> >> >> > Meino |
36 |
> >> >> > |
37 |
> >> >> |
38 |
> >> >> Markdown is a markup language that was specifically designed to be |
39 |
> >> readable in the source. |
40 |
> >> >> |
41 |
> >> >> However, if you still find it hard to read, perhaps syntax |
42 |
> >> highlighting in a fancy |
43 |
> >> >> text editor can help approximate the intended effects of the markup. |
44 |
> >> >> |
45 |
> >> >> Also, there are markdown-to-HTML translators. Some are even included |
46 |
> >> in portage tree. |
47 |
> >> >> |
48 |
> >> > |
49 |
> >> > |
50 |
> >> > I dont want to convert the md-files to html, since I want to update |
51 |
> >> > the repo later (see above). |
52 |
> >> > The problem are files referencing other files. Reading the md-files |
53 |
> >> > via vim (for example) would imply to grab all references by hand. |
54 |
> >> > Fortheremore, tne docs are filled with graphics (for example images |
55 |
> >> > of the fonts, which can be used), which cannot be displayed with an |
56 |
> >> > ASCII-editor. |
57 |
> >> > Formatting is necassary with this docs... |
58 |
> >> > |
59 |
> >> |
60 |
> >> Typically what is done is you render the whole Wiki to HTML, and then |
61 |
> >> view it in a browser. You don't edit the HTML directly. It should be |
62 |
> >> possible to generate it incrementally. |
63 |
> >> |
64 |
> >> The one catch is that they might be relying on GitHub's integrated |
65 |
> >> Wiki system. If they are, you might need to install Gollum to process |
66 |
> >> the markdown files to HTML. |
67 |
> >> |
68 |
> >> Cheers, |
69 |
> >> R0b0t1 |
70 |
> >> |
71 |
> >> |
72 |
> > This is a definite overkill, but I'm using JetBrains' IntelliJ Idea |
73 |
> > (actually PyCharm) with the markdown plugin. It shows markdown and html |
74 |
> > side-to-side in the editor. |
75 |
> > |
76 |
> > Anton |
77 |
> > |
78 |
> > |
79 |
|
80 |
|
81 |
Hello all, |
82 |
|
83 |
thanks a lot for all the reponses to my question. |
84 |
|
85 |
I found a Firefox-Plugin, which is able to render |
86 |
markdown on the fly. It is here: |
87 |
https://addons.mozilla.org/en-US/firefox/addon/markdown-viewer-webext/?src=search |
88 |
|
89 |
Despite the comment of one user, it DOES display local markdown |
90 |
formatted files...just with a small little delay... |
91 |
|
92 |
Cheers |
93 |
Meino |