Visit Our UNIX and Linux User Community

Contact Us Post Here to Contact Site Administrators and Moderators Question regarding my blog-thread Post 303046078 by Neo on Thursday 23rd of April 2020 09:06:28 AM
Old 04-23-2020
Normally, all attachments uploaded to the forums should be in format:

Code:
[ATTACH]integer_id[/ATTACH]

This is how attachment inserted correctly into the forum posts will look when you edit the post.

Here is an example from one of my posts (in the editor);

Question regarding my blog-thread-screen-shot-2020-04-23-80547-pmjpg


The reason I hid my post is that we will be moving to the new forums soon, and I did not want to annoy you about this.
This User Gave Thanks to Neo For This Post:
 
Test Your Knowledge in Computers #192
Difficulty: Medium
Hello World in Python looks like this: printLine('Hello, world!')
True or False?

3 More Discussions You Might Find Interesting

1. Programming

How to cancel a thread safely from the initial thread?

how about asynchronous canceling? or with signal? if with signal whether it effects the process? my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies

2. Programming

Question on creation of Thread pool

dear sir/madam presently i am in a process of creating a multithread pool using clone() system call in unix with c programming. i am facing some problem ie., i am able create multithread pool and able to keep all the threads in wait state,but when i call kill (afunction revoke a... (6 Replies)
Discussion started by: Radha
6 Replies

3. Shell Programming and Scripting

Blog-Thread: Creating a Shell Wrapper and Runtime Modifier (SWARM)

SWARM = Shell Wrapper and Runtime Modifier But as a matter of fact, it's more like a Text User Interface framework for scripts. Which was the original title (TUI) of the first split-up iteration from Script-Tools. Script-Tools is still the 'end/final-project', SWARM is just the way to get... (32 Replies)
Discussion started by: sea
32 Replies
CHRONICLE-ENTRY-FILTER(1)				User Contributed Perl Documentation				 CHRONICLE-ENTRY-FILTER(1)

NAME
chronicle-entry-filter - Convert blog files to HTML, if required. SYNOPSIS
Help Options --help Show a brief help overview. --version Show the version of this script. Options --format The global format of all entries. --filename The name of the single file to process. Filters --pre-filter A filter to run before convertion to HTML. --post-filter A filter to run after HTML conversion. ABOUT
This script is designed to receive a filename and a global formatting type upon the command line. The formatting type specifies how the blog entry file will be processed: 1. If the format is "textile" the file will be converted from textile to HTML. 2. If the format is "markdown" the file will be converted from markdown to HTML. The related format "multimarkdown" is also recognised. 3. If the format is "html" no changes will be made. Once the conversion has been applied the code will also be scanned for <code> tags to expand via the Text::VimColour module, if it is installed, which allows the pretty-printing of source code. To enable the syntax highlighting of code fragments you should format your code samples as follows: Subject: Some highlighted code. Date: 25th December 2009 Tags: chronicle, perl, blah <p>Here is some code which will look pretty ..</p> <code lang="perl"> #!/usr/bin/perl -w ... .. </code> Notice the use of lang="perl", which provides a hint as to the type of syntax highlighting to apply. Additionally you may make use of the pre-filter and post-filter pseudo-headers which allow you to transform the entry in further creative fashions. For example you might wish the blog to be upper-case only for some reason, and this could be achieved via: Subject: I DONT LIKE LOWER CASE Tags: meta, random, silly Date: 25th December 2009 Pre-Filter: perl -pi -e "s/__USER__/`whoami`/g" Post-filter: tr [a-z] [A-Z] <p>This post, written by __USER__ will have no lower-case values.</p> <p>Notice how my username was inserted too?</p> You may chain arbitrarily complex filters together via the filters. Each filter should read the entry on STDIN and return the updated content to STDOUT. (If you wish to apply a global filter simply pass that as an argument to chronicle, or in your chroniclerc file.) AUTHOR
Steve -- http://www.steve.org.uk/ LICENSE
Copyright (c) 2009-2010 by Steve Kemp. All rights reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The LICENSE file contains the full text of the license. perl v5.12.3 2011-05-03 CHRONICLE-ENTRY-FILTER(1)

Featured Tech Videos

All times are GMT -4. The time now is 07:04 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy