Closed (fixed)
Project:
GeSHi Filter for syntax highlighting
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 May 2011 at 19:45 UTC
Updated:
26 Apr 2017 at 23:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
setvik commentedUpdated comments at file top to reflect new Drupal version (Drupal 7)
Comment #2
setvik commentedUpdated comments at file top to reflect new Drupal version (Drupal 7)
Comment #3
setvik commentedComment #5
soxofaan commentedHi,
Thanks for the drupal7 file! There seem to be some indentation issues though (not very critical).
How did you generate it? Did you use the script from #179470: Drupal Highlighting for GeSHi?
Comment #6
setvik commentedi didn't realize that script was there... nuts, that would've saved some time... i ended up writing a script in PHP to extract functions and constants...
There are a couple of things to note:
http://api.drupal.org/api/function/db_query/7to:
http://api.drupal.org/api/drupal/includes--database--database.inc/function/db_query/7api.drupal.org redirects the former to the latter. The only way i can see to accomodate the new URL pattern in geshi (and avoid a redirect) would be to group the function names and constants by file which would make it possible to specify a URL pattern per drupal file. I haven't tested it, but i suspect it would be a performance hit. I generated the above file using the old url pattern.
Comment #7
soxofaan commented1. I think it's ok to use the old format, supporting the new format would increase the number of groups massively
2. Too bad classes are not supported in the old format. Doing it with separate groups will look silly I'm afraid: there will be one or two classes per group I guess. Maybe just leave doc link support for classes out of it for the moment?
Comment #8
boobaaI think the best approach would be asking api.module guys how do they do their magic, and have something that can generate all the needed stuff for geshifilter.module based on their code, or something alike. Don't know if it really fits here, though, and don't know if handling all the classes, files and whatsoever as "groups" mentioned above would be a performance hit or not.
OTOH, there is another question here, I think: which is the bigger PITA: the man-hours to generate the file geshifilter.module needs (either "by hand" or "by code"), or the performance hit caused by that quite a bunch of "groups" (if any)?
Comment #9
yukare commentedThere is something missing on this or we just need to add it to git ?
Comment #10
rosk0I think we just need to commit it, it works.
Comment #11
gisleAdded alternate method for flushing language cache.
Comment #12
delacosta456 commentedHi i was facing this issue with Drupal 7.53 and Geshi 1.08.11
and Step 1 to 4 solve it for me.
thanks
Comment #14
yukare commentedCommited, thanks!