my development scratches

openrisc development

View My GitHub Profile

Welcome to git-wiki demo

This is a demo of git-wiki theme for jekyll.

it’s a full featured wiki powered by git, github pages and pull-requests!

It means:

  • Improvements in the cooperative aspect: forks, pull-requests and roles.
  • You can customize your wiki as you want with style sheets and even changing the layout.
  • No databases! Only static files that can be downloaded in a few seconds.
  • Markdown and html mixed together!
  • History, revision comparison and everything you need from a wiki platform.
  • You can edit your pages with the standard git editor, prose.io (integrated) or any kind of editor you prefer.

You can fork/copy the master branch now and start your wiki in just 1 minute.

Then share your wiki with us! please.

Note: You can even include the github wiki as a submodule and enable the conf, but it’s an experimental feature and it implies less advantages and greater disadvantages for now.

Installation instructions

  1. Fork or copy this repository

  2. copy and rename _config.yml.dist in _config.yml changing settings inside

  3. create your index.md in root directory

  4. push your changes in your repository, then configure the github pages in your repository settings

  5. Your wiki is ready!

Note:

We suggest the creation of a /wiki/ subfolder that collects all your .md pages (except index.md)

Current known limitations

  • Non-existent wiki page links are not “red”.

  • You can’t use the wiki link format: [[example]]. Please, use gh-pages links instead: [example](example)

Customization

You can create following files in _includes folder to costumize git-wiki without patching original code:

  • head.html -> this file will be included in <head> tag allowing you to add css/js and any kind of head tags
  • sidebar.html -> this file will be included in left sidebar allowing you to create your widgets
  • comments.html -> this is mostly used to integrate social comments under page contents
  • footer.html -> this file will be included in left side of the footer.

Looking for collaboration

Do you like this project? then, contact us via chat , email or send us a PR to improve it.

Thank you!

headers

# H1

## H2

### H3

#### H4

##### H5

H1
====

H2
----

H1

H2

H3

H4

H5

H1

H2

numbering

  1. hello

  2. world

  3. foo
    • sub bullet
  4. bar
    • hello
    • world
    • foo
    • bar
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

Or leave it empty and use the [link text itself].

URLs and URLs in angle brackets will automatically get turned into links. 
http://www.example.com or <http://www.example.com> and sometimes 
example.com (but not on Github, for example).

Some text to show that the reference links can follow later.

[arbitrary case-insensitive reference text]: https://www.mozilla.org
[1]: http://slashdot.org
[link text itself]: http://www.reddit.com

I’m an inline-style link

I’m an inline-style link with title

I’m a reference-style link

I’m a relative reference to a repository file

You can use numbers for reference-style link definitions

Or leave it empty and use the link text itself.

URLs and URLs in angle brackets will automatically get turned into links. http://www.example.com or http://www.example.com and sometimes example.com (but not on Github, for example).

Some text to show that the reference links can follow later.

images

Here's our logo (hover to see the title text):

Inline-style: 
![alt text](https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 1")

Reference-style: 
![alt text][logo]

[logo]: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 2"

Here’s our logo (hover to see the title text):

Inline-style: alt text

Reference-style: alt text

table

헤더1 헤더2 헤더3
컬럼1 컬럼2 컬럼3
컬럼4 컬럼5 컬럼6
컬럼1 컬럼2 컬럼3
컬럼4 컬럼5 컬럼6
     
컬럼1 컬럼2 컬럼3
컬럼4 컬럼5 컬럼6
Foot1 Foot2 Foot3
|             |          Grouping           ||
|First Header | Second Header | Third Header |
|-------------|:-------------:|-------------:|
|Content      |          *Long Cell*        ||
|Content      |   **Cell**    |         Cell |
|New section  |     More      |         Data |
|And more     | With an escaped '\|'        ||  
[Prototype table]
  Grouping  

|First Header | Second Header | Third Header | |————-|:————-:|————-:| |Content | Long Cell || |Content | Cell | Cell | |New section | More | Data | |And more | With an escaped ‘|’ ||
[Prototype table]

| | Grouping || |First Header | Second Header | Third Header | |————-|:————-:|————-:| |Content | Long Cell || |Content | Cell | Cell | |New section | More | Data | |And more | With an escaped ‘|’ ||
[Prototype table]

line break

some

***


foo

___


bar

---


code block

Inline `code` has `back-ticks around` it.

Inline code has back-ticks around it.

```` c
#include <stdio.h>

int main(void)
{
    printf("Hello word!\n");
    return 1;
}
````
~~~~ c
#include <stdio.h>

int main(void)
{
    printf("Hello word!\n");
    return 1;
}
~~~~
#include <stdio.h>

int main(void)
{
    printf("Hello word!\n");
    return 1;
}
s = 'Hello word'
print(s)
module test;

initial
begin
    $display("Hello world");
    $finish;
end

endmodule
(df f-disp21
    "disp21"
    ((MACH ORBIS-MACHS) ABS-ADDR)
    20
    21
    INT
    ((value pc)
     (sub IAI (sra IAI value (const 13)) (sra IAI pc (const 13))))
    ((value pc)
     (sll IAI (add IAI value (sra IAI pc (const 13))) (const 13)))
    )
#!/usr/local/bin/perl -w

use Getopt::Long;
use POSIX;

GetOptions(
    "help|h|?"          => \$opt{"help"},
    "address|a=s"       => \$opt{"addr"},
    "destination|d=s"   => \$opt{"dst"},
    "shift|s=s"         => \$opt{"shift"}
    );

if( defined $opt{"help"} || !defined $opt{"dst"} || !defined $opt{"addr"}){
    print <<END_OF_HELP;
Usage: wav2srec.pl -a start_address [-s shift] -d srecfile.srec wavfile1.wav [wavfile2.wav [...]]
       default shift : 2
END_OF_HELP
    exit(1);
}
if ($uver =~ *el5*) then
    set centos_ver = '5'
else if ($uver =~ *el6*) then
    set centos_ver = '6'
else if ($uver =~ *el7*) then
    set centos_ver = '7'
else
    set centos_ver = '0'
endif
# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth
    @Throws(HidException::class)
    fun write(data: ByteArray, size: Int = packetSize) {
        val status = connection!!.bulkTransfer(endPointWrite, data, size, write_timeout)
        if (status < 0)
            throw HidException()
    }
    @Override
    protected void onStart(){
        super.onStart();
        Log.v("wang", "Sensor_Start");
        hidSetup();
    }
    @Override
    protected void onPause(){
        super.onPause();
        Log.v("wang", "Sensor_Pause");
    }

Components used

MIT LICENSE